Hi devs,
Currently XWiki Watch is built as a XWiki application, with no server code,
distributable as a xar archive, using only xwiki-web-gwt's XWikiService to
communicate with XWiki.
While this approach has major advantages from the application accessibility
point of view (it can be easily downloaded and installed), the drawback is the
big amount of functionality that needs to be implemented on the client side
(even if with GWT), with main impact on the application performance (javascript
execution in the browser, data transfer, asynchronous calls).
I propose to change the current approach and create XWatch server / service and
distribute XWatch as a zip / war because:
* it improves code performance: less javascript to execute on client side, less
network traffic; lighter for the client overall
* removing the .xar constraint and distributing watch as zip / war would allow
XWatch dependency on plugins / modules versions independent from XE.
* some Watch features already need some kind of administration on the hosting
machine (emailing press reviews needs a running mail delivery system on the server).
As I mentioned already, the only thing we would lose through this change is the
possibility of installing XWatch as a simple xar (I am not currently very aware
of the amount of users downloading and installing watch as a .xar and not being
able to do it otherwise, so if you can give me some info on that...)
Since I feel the gains would be above the losses, I am +1 for the switch, WDYT?
Hi Jerome,
see below
On Aug 6, 2008, at 12:53 PM, jvelociter (SVN) wrote:
> Author: jvelociter
> Date: 2008-08-06 12:53:03 +0200 (Wed, 06 Aug 2008)
> New Revision: 11685
>
> Added:
> platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/
> platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/
> platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/
> com/
> platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/
> com/xpn/
> platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/
> com/xpn/xwiki/
> platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/
> com/xpn/xwiki/tool/
> platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/
> com/xpn/xwiki/tool/doc/
> platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/java/
> com/xpn/xwiki/tool/doc/UpdateDocumentMojoTest.java
> platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/
> resources/
> platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/
> resources/SampleWikiXMLDocument.input
> Log:
> XTXMLDOC-6 XClasses lost when exporting documents with existing
> objects
> * Added a test that proves we lose classes when writting back the
> doc to XML.
>
>
> Added: platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/
> test/java/com/xpn/xwiki/tool/doc/UpdateDocumentMojoTest.java
> ===================================================================
> --- platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/
> java/com/xpn/xwiki/tool/doc/
> UpdateDocumentMojoTest.java (rev 0)
> +++ platform/xwiki-tools/trunk/xwiki-xmldoc-update-plugin/src/test/
> java/com/xpn/xwiki/tool/doc/UpdateDocumentMojoTest.java 2008-08-06
> 10:53:03 UTC (rev 11685)
> @@ -0,0 +1,85 @@
> +/*
> + * See the NOTICE file distributed with this work for additional
> + * information regarding copyright ownership.
> + *
> + * This is free software; you can redistribute it and/or modify it
> + * under the terms of the GNU Lesser General Public License as
> + * published by the Free Software Foundation; either version 2.1 of
> + * the License, or (at your option) any later version.
> + *
> + * This software is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
> + * Lesser General Public License for more details.
> + *
> + * You should have received a copy of the GNU Lesser General Public
> + * License along with this software; if not, write to the Free
> + * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA
> + * 02110-1301 USA, or see the FSF site: http://www.fsf.org.
> + */
> +package com.xpn.xwiki.tool.doc;
> +
> +import java.io.File;
> +import java.io.FileReader;
> +import java.io.IOException;
> +import java.net.URL;
> +
> +import org.apache.maven.plugin.MojoExecutionException;
> +
> +import com.xpn.xwiki.doc.XWikiDocument;
> +
> +import junit.framework.TestCase;
> +
> +/**
> + * Test for {@link AbstractDocumentMojo}
> + *
> + * @version $Id: $
> + */
> +public class UpdateDocumentMojoTest extends TestCase
> +{
> +
> + /**
> + * Test that a document loaded in memory from XML by the mojo
> then written back to XML does not lose any
> + * information/is not affected by the process
> + */
> + public void testXMLDocumentLoading()
> + {
> + AttachMojo mojo = new AttachMojo();
> + URL resURL = this.getClass().getResource("/
> SampleWikiXMLDocument.input");
> + try {
> + File resourceFile = new File(resURL.getPath());
> + XWikiDocument doc = mojo.loadFromXML(resourceFile);
> + FileReader fr = new FileReader(resourceFile);
> + char[] bytes = new char[(int) resourceFile.length()];
> + fr.read(bytes);
> + String inputContent = new String(bytes);
> +
> + assertTrue(inputContent.contains("<class>"));
> +
> + assertEquals(doc.getName(), "Install");
> +
> + File outputFile = File.createTempFile("output", "xml");
> + mojo.writeToXML(doc, outputFile);
> +
> + fr = new FileReader(outputFile);
> + bytes = new char[(int) outputFile.length()];
> + fr.read(bytes);
> + String outputContent = new String(bytes);
> +
> + // Test that prove class definitions are lost during
> the process of loading/writing back the XML document.
> + // It currently fail, see http://jira.xwiki.org/jira/browse/XTXMLDOC-6
> + assertTrue(outputContent.contains("<class>"));
> +
> + // check there is no diff bewteen input and output
> file, as no transformation
> + // has been applied.
> + assertEquals(inputContent, outputContent);
> +
> + } catch (MojoExecutionException e) {
> + fail();
> + } catch (IOException e) {
> + fail("Could not load wiki xml document resource file.");
> + }
The best practice is to not use a try/catch block and instead have the
test signature throws an Exception. That's unless you're specifically
testing for an exception but that's not the case here.
Thanks
-Vincent
Hi,
I just upgraded my system and before that Xwiki was running fine. Now, it is
giving me error
HTTP ERROR: 500
Error number 3 in 0: Could not initialize main XWiki context
Wrapped Exception: Error number 3001 in 3: Cannot load class
com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager
from param xwiki.store.migration.manager.class
Wrapped Exception: net.sf.cglib.proxy.Enhancer
RequestURI=/xwiki/bin/view/XWSAdmin/
Complete logs here : http://pastie.org/249438
Please help, it's been more than couple of hours since I am stuck in this. I
didn't change any configuration during kernel upgrade.
--
Arpit Jain
http://www.intinno.com
Hi devs,
I have complied the content assistance for xwiki API.Now the proposals are
readout from a seperate resource file.There are seperate file for each
context type ( i.e seperate files for $xwiki ,$doc .. ) .At the moment the
API information is stored in the files in the following format
xwiki.copyDocument(java.lang.String docname, java.lang.String
sourceWiki,java.lang.String targetWiki, java.lang.String wikilanguage)
is transtatet to
a single line entry in the xwiki.txt resourse file as bellow
copyDocument String docname String sourceWiki String targetWiki
String wikilanguage
Now i'm looking at velocity variable proposal and error notification.In
order to provide content assistance and error marking, there is a
requirement to parse and build the an object model of document which
contains both XWiki and Velocity. AFAIK, XDOM only supports XWiki. Is there
an object model which can r present these two languages.
For velocity code, there is a possibility to use the parser shipped with
Apache Velocity. But then we need to develop our own object model.
Any help would be greatly appreciated.
-- Malaka
Hello,
Do you foresee a special syntax for groovy scripts as you already have for
velocity using {{velocity}} with some more features?
My idea is to be able to code cleanly using groovy and to put some "generic"
part of scripts in separated documents and to be able to import them in
other docs containing other parts of scripts.
It would be really nice to be able to type some part of scripts or to define
some groovy classes in a page and tell "this is groovy code which is not
"WIKI-renderable" as is".
Then we could simply import/include this script in another page (just paste
the code without any rendering) using something like
#include("MySpace.MyGroovyDoc").
xwiki.parseGroovyXXX is useful sometimes but not when you only want to
include some part of scripts.
Existing #includeXXX macros always render the content and here I only want
to paste a script from somewhere else (xwiki.getDocument("").getContent() in
fact)
Moreover the idea would be also to allow using both "xwiki.parseGroovy" and
the #include macro for the same groovy "document". For the time being, one
need to use the trick
/* groovygroovy #* */
/* *# */
and then you are condemned to use xwiki.parseGroovyXXX because no other
function can interprete this tricky syntax.
best regards
Pascal
We should try it. Who's game to upgrade our FOP version and verify our
PDF/RTF exports still work?
Thanks
-Vincent
Begin forwarded message:
> From: Jeremias Maerki <jeremias(a)apache.org>
> Date: August 6, 2008 8:05:47 AM CEDT
> To: fop-dev(a)xmlgraphics.apache.org, fop-
> users(a)xmlgraphics.apache.org, general(a)xmlgraphics.apache.org, general(a)xml.apache.org
> , announce(a)apache.org, XSL-FO(a)yahoogroups.com, www-xsl-fo(a)w3.org
> Subject: [ANN] Apache FOP 0.95 Released
>
> Apache FOP (Formatting Objects Processor) is a print formatter
> driven by
> XSL Formatting Objects [1] and an output independent formatter. It
> is a
> Java application that reads a formatting object tree and renders the
> resulting pages to a specified output. Output formats currently
> supported include PDF, PS, PCL, AFP, Print and TIFF/PNG. Apache FOP is
> Open Source software and published under the Apache License v2.0.
>
> It took longer than expected but we're happy to present the final
> Apache
> FOP 0.95 stable release. This is basically a bugfix release to
> 0.95beta.
> The most important changes since the previous stable release (0.94)
> are:
> - many bug fixes and improvements in tables, better support for keeps
> and breaks, new features: conditional borders and background on
> columns and header/footer/body;
> - better image handling thanks to the new image loading framework
> provided by the Apache XML Graphics Commons dependency;
> - improvements and bugfixes for font handling and font
> auto-detection/-registration;
> - performance improvements and memory optimizations for the property
> handling in the FO tree.
> - elimination of a potential multi-threading problem.
> - some feature enhancements for RTF output (partial fo:leader support,
> fo:page-number-citation)
>
> Please note that support for Java 1.3 has been dropped. Only one
> type of
> binaries is provided now, that will run on 1.4+ JREs.
>
> Other important release notes are available at
> http://xmlgraphics.apache.org/fop/0.95/releaseNotes_0.95.html
>
> For a more complete list of changes, please visit
> http://xmlgraphics.apache.org/fop/0.95/changes_0.95.html
>
> For download information, see the following page:
> http://xmlgraphics.apache.org/fop/download.html
>
>
> [1] http://www.w3.org/TR/xsl11/
>
>
> On behalf of the Apache XML Graphics team,
> Jeremias Maerki
Hi,
I am student with RMIT University and I am working on a project on open-source wiki application. I have a basic idea of velocity, struts, eclipse, maven, java, xml, etc. as a part of the courses that I am doing in university. Thats is why I looked at the xwiki workspace application.
To build my project, I went thru various helps available at xwiki site like:
- http://dev.xwiki.org
- http://platform.xwiki.org
I want to study the source code so that I can understand it better. So, I want to see the source code in eclipse. I went thru the help on above site but I am not sure how to deploy the code in eclipse. I wanted this to do this to make changes in the code and run it to see how it affects the existing environment.
In my earlier projects, I had the distribution of files (.war) which included both source and classes, but xwiki_workspaces.war has only class distribution. So, i am unable to make changes and see its affects.
Any help would be appreciated.
ac
Hi,
Is there any way to access to page object attributes and/or unrendered page
content ? Thanks in advance.
--
Hoani CROSS
Globotraders Tahiti Founder [http://globotraders-tahiti.com]