- xwiki-devs@xwiki.org - lists.xwiki.org

Re: [xwiki-devs] [xwiki-notifications] r25288 - enterprise/trunk/distribution-test/xmlrpc-tests/src/test/it/com/xpn/xwiki/it/xmlrpc enterprise/trunk/distribution-test/xmlrpc-tests/src/test/it/org/xwiki/xmlrpc platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc platform/core/trunk/xwiki-xmlrpc/xwiki-xmlrpc-client/src/main/java/org/xwiki/xmlrpc platform/core/trunk/xwiki-xmlrpc/xwiki-xmlrpc-model/src/main/java/org/xwiki/xmlrpc

by Sergiu Dumitriu

On 11/26/2009 04:28 PM, tmortagne (SVN) wrote: > Author: tmortagne > Date: 2009-11-26 16:28:25 +0100 (Thu, 26 Nov 2009) > New Revision: 25288 > > Added: > enterprise/trunk/distribution-test/xmlrpc-tests/src/test/it/org/xwiki/xmlrpc/RenderingTest.java > Modified: > enterprise/trunk/distribution-test/xmlrpc-tests/src/test/it/com/xpn/xwiki/it/xmlrpc/AllTests.java > platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiXmlRpcApiImpl.java > platform/core/trunk/xwiki-xmlrpc/xwiki-xmlrpc-client/src/main/java/org/xwiki/xmlrpc/XWikiXmlRpcClient.java > platform/core/trunk/xwiki-xmlrpc/xwiki-xmlrpc-model/src/main/java/org/xwiki/xmlrpc/XWikiXmlRpcApi.java > Log: > XWIKI-4464: Extend the XmlRpc API with new rendering features > * Apply patch from Florin Ciubotaru: > ** New getRenderedContendMethods added to the api(We still need a few votes on devs for these to get commited). Completed the client with the new additions. > ** Added integration tests. > > Modified: enterprise/trunk/distribution-test/xmlrpc-tests/src/test/it/com/xpn/xwiki/it/xmlrpc/AllTests.java > =================================================================== > --- enterprise/trunk/distribution-test/xmlrpc-tests/src/test/it/com/xpn/xwiki/it/xmlrpc/AllTests.java 2009-11-26 11:14:42 UTC (rev 25287) > +++ enterprise/trunk/distribution-test/xmlrpc-tests/src/test/it/com/xpn/xwiki/it/xmlrpc/AllTests.java 2009-11-26 15:28:25 UTC (rev 25288) > @@ -62,6 +62,7 @@ > addTestCase(suite, org.xwiki.xmlrpc.XWikiClassesTest.class); > addTestCase(suite, org.xwiki.xmlrpc.XWikiObjectsTest.class); > addTestCase(suite, org.xwiki.xmlrpc.SearchTest.class); > + addTestCase(suite, org.xwiki.xmlrpc.RenderingTest.class); > > return new XWikiTestSetup(suite); > } > > Added: enterprise/trunk/distribution-test/xmlrpc-tests/src/test/it/org/xwiki/xmlrpc/RenderingTest.java > =================================================================== > --- enterprise/trunk/distribution-test/xmlrpc-tests/src/test/it/org/xwiki/xmlrpc/RenderingTest.java (rev 0) > +++ enterprise/trunk/distribution-test/xmlrpc-tests/src/test/it/org/xwiki/xmlrpc/RenderingTest.java 2009-11-26 15:28:25 UTC (rev 25288) > @@ -0,0 +1,145 @@ > +/* > + * 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 org.xwiki.xmlrpc; > + > +import java.util.List; > + > +import junit.framework.Assert; > + > +import org.apache.xmlrpc.XmlRpcException; > +import org.xwiki.xmlrpc.model.XWikiPage; > + > +public class RenderingTest extends AbstractXWikiXmlRpcTest > +{ > + public void testGetInputSyntaxes() throws XmlRpcException > + { > + List<String> syntaxes = rpc.getInputSyntaxes(); > + > + TestUtils.banner("TEST: getInputSyntaxes()"); I'd swap the banner setting and the retrieval method, since if the method fails, then the banner won't be set. Also, System.out should not be used. > + System.out.format("%d conversion input syntaxes found:\n", syntaxes.size()); > + for (String syntaxId : syntaxes) { > + System.out.format("%s\n", syntaxId); > + } > + Assert.assertTrue(syntaxes.size() != 0); > + } > + > + public void testGetOutputSyntaxes() throws XmlRpcException > + { > + List<String> syntaxes = rpc.getOutputSyntaxes(); > + > + TestUtils.banner("TEST: getOutputSyntaxes()"); > + System.out.format("%d conversion output syntaxes found:\n", syntaxes.size()); > + for (String syntaxId : syntaxes) { > + System.out.format("%s\n", syntaxId); > + } > + Assert.assertTrue(syntaxes.size() != 0); > + } > + > + public void testConvert() throws XmlRpcException > + { > + String inputXWiki = > + "**BoldText**//ItalicText//" + String.format("%n") + "==h2Text==" + String.format("%n") + "normalText"; Why String.format("%n")? Doesn't a simple \n suffice? Or, if the reak system endline must be used, for a reason I can't see now, how about org.apache.commons.lang.SystemUtils.LINE_SEPARATOR or the raw System.getProperty("line.separator")? > + String inputXhtml = > + "<div><p><strong>boldText</strong><br/><em>ItalicText</em></p>" + String.format("%n") > + + "<h2 id=\"h2Text\"><span>h2Text</span></h2><p>normalText</p></div>"; > + > + TestUtils.banner("TEST: convert()"); > + System.out.format("\nTesting xwiki/2.0 -> xhtml/1.0 conversion\n"); > + System.out.format("Input text:\n%s", inputXWiki); > + > + String outputXhtml = rpc.convert(inputXhtml, "xwiki/2.0", "xhtml/1.0"); > + > + System.out.format("\nOutput text:\n%s", outputXhtml); > + > + Assert.assertNotNull(outputXhtml); > + Assert.assertFalse(outputXhtml.equals("")); You could also test some generated markup here. > + Assert.assertTrue(outputXhtml.contains("strong")); > + Assert.assertTrue(outputXhtml.contains("normalText")); > + Assert.assertTrue(outputXhtml.contains("ItalicText")); > + > + System.out.format("\nTesting xhtml/1.0 -> xwiki/2.0 conversion\n"); > + System.out.format("Input text:\n%s", inputXhtml); > + > + String outputXWiki = rpc.convert(inputXhtml, "xhtml/1.0", "xwiki/2.0"); > + > + System.out.format("\nOutput text:\n%s\n", outputXWiki); > + > + Assert.assertNotNull(outputXWiki); > + Assert.assertFalse(outputXhtml.equals("")); > + Assert.assertTrue(outputXhtml.contains("normalText")); > + Assert.assertTrue(outputXhtml.contains("ItalicText")); > + } > + > + public void testGetRenderedContent() throws XmlRpcException > + { > + String pageContent = "**Text in Bold**{{velocity}}VelocityCode{{/velocity}}"; > + > + XWikiPage page = new XWikiPage(); > + page.setId(TestConstants.TEST_PAGE); > + page.setContent(pageContent); > + page.setSyntaxId("xwiki/2.0"); > + > + TestUtils.banner("TEST: getRenderedContent()"); > + System.out.format("\nCalling getRenderedContent for page %s\n", page.getId()); > + System.out.format("\nWiki content is:\n%s\n", pageContent); > + > + rpc.storePage(page); > + > + try { > + String renderedContent = rpc.getRenderedContent(page.getId(), "annotatedxhtml/1.0"); > + > + System.out.format("\nObtained rendered content:\n%s\n\n", renderedContent); > + > + Assert.assertTrue(renderedContent.contains("Text in Bold")); > + Assert.assertTrue(renderedContent.contains("startmacro")); > + } finally { > + rpc.removePage(page.getId()); > + } > + } > + > + public void testRenderPageContent() throws XmlRpcException > + { > + String pageContent = "**Text in Bold**{{velocity}}VelocityCode{{/velocity}}"; > + > + XWikiPage page = new XWikiPage(); > + page.setId(TestConstants.TEST_PAGE); > + page.setContent(pageContent); > + page.setSyntaxId("xwiki/2.0"); > + > + TestUtils.banner("TEST: renderPageContent"); > + System.out.format("\nCalling renderPageContent with context as page %s\n", TestConstants.TEST_PAGE); > + System.out.format("\nWiki content is:\n%s\n", pageContent); > + > + rpc.storePage(page); > + > + try { > + String renderedContent = > + rpc.renderPageContent(page.getId(), page.getContent(), page.getSyntaxId(), "annotatedxhtml/1.0"); > + > + System.out.format("\nObtained rendered content:\n%s\n\n", renderedContent); > + > + Assert.assertTrue(renderedContent.contains("Text in Bold")); > + Assert.assertTrue(renderedContent.contains("startmacro")); > + } finally { > + rpc.removePage(page.getId()); > + } > + } > +} > > > Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiXmlRpcApiImpl.java > =================================================================== > --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiXmlRpcApiImpl.java 2009-11-26 11:14:42 UTC (rev 25287) > +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiXmlRpcApiImpl.java 2009-11-26 15:28:25 UTC (rev 25288) > @@ -1455,4 +1455,47 @@ > } > return syntaxes; > } > + > + /** > + * Renders a text in the context of a wiki page. > + * > + * @param token The authentication token. > + * @param pageId The id of the page. > + * @param content The context to be rendered. > + * @param sourceSyntaxId The syntax of the content. > + * @param targetSyntaxId The target syntax of the rendered content > + * @return The rendered content. > + * @throws Exception If a invalid token is provided, an unsupported syntax id is given or the rendering fails. > + */ Make sure a user can't use the programming rights of a page to interpret his own text. > + public String renderPageContent(String token, String pageId, String content, String sourceSyntaxId, > + String targetSyntaxId) throws Exception > + { > + XWikiXmlRpcUser user = XWikiUtils.checkToken(token, this.xwikiContext); > + LOG.debug(String.format("User %s has called renderPageContent()", user.getName())); > + > + Document doc = XWikiUtils.getDocument(this.xwikiApi, pageId, true); > + > + return doc.getRenderedContent(content, sourceSyntaxId, targetSyntaxId); > + } > + > + /** > + * Gets the rendered content of an existing document. > + * > + * @param token The authentication token. > + * @param pageId The id of the page. > + * @param syntaxId The target syntax of the rendered content > + * @return The rendered content > + * @throws Exception If a invalid token is provided, an unsupported syntax id is given or the rendering fails. > + */ > + public String getRenderedContent(String token, String pageId, String syntaxId) throws Exception > + { > + XWikiXmlRpcUser user = XWikiUtils.checkToken(token, this.xwikiContext); > + LOG.debug(String.format("User %s has called getRenderedContent()", user.getName())); > + > + Document doc = XWikiUtils.getDocument(this.xwikiApi, pageId, true); > + SyntaxFactory syntaxFactory = Utils.getComponent(SyntaxFactory.class); > + Syntax syntax = syntaxFactory.createSyntaxFromIdString(syntaxId); > + > + return doc.getRenderedContent(syntax); > + } > } > -- Sergiu Dumitriu http://purl.org/net/sergiu/

15 years, 9 months

1
0
0 0

[xwiki-devs] Generate URL Link and Save it in WYSIWYG editor

by Leon Wang

Hi Devs, Hi Marius, Could you give me some clues how to generate and save a page url that could locate to the position of a certain title/section of the article within the WYSIWYG editor, for example like this url, http://platform.xwiki.org/xwiki/bin/view/DevGuide/APIGuide#HAccessobjectsin…, click this link it will bring me to "Access objects in a page" subtitle. What I want to achieve is that in the WYSIWYG editor after I highlighted a sentence and clicked the Requirement tree node, it will highlight the background of the text and generate a link to the highlighted text, so this generated link could bring designer/system maintainer to the context of the document. Could you point me to the place of your WYSIWYG editor source code that I need to add/change? Do you know how can I get the value of the selected text, should I directly right javascript or should I modify your WYSIWYG source code? Thank you so much! Have a nice new week! Jue Wang (Leon)

15 years, 9 months

1
0
0 0

[xwiki-devs] XOO

by Cristina Scheau

Hi all! How are you? I apologize that I wasn't so active recently. I spent all my time with tasks from my job and my Master. Now I have a little bit more free time (in the evenings and weekends) and I would like to continue the XOO project. I'm not clear what should I exactly do next and maybe you can help me with your feedback and ideas. I'd really like to contribute again to the XWiki software . Although I was not so happy with the API from OpenOffice , last summer was a really interesting experience for me. Thank you, Cristina S.

15 years, 9 months

1
0
0 0

[xwiki-devs] [VOTE] New tool, xwiki-tool-standards-validator

by Jean-Vincent Drean

Hi, I'd like to commit a new standalone tool, xwiki-tool-standards-validator, it allows to run XHTML and Dutch Web Guidelines validation tests (only a few rules for the moment) on an InputStream. This tool will be used by a new enterprise module that I'll commit right after, xwiki-enterprise-test-webstandards which runs the validators on every pages present in the XE distrib. Here's my +1, JV.

15 years, 9 months

7
12
0 0

Re: [xwiki-devs] [xwiki-users] Page Loading Optimization

by Jerome Velociter

Hi Thibaul, all Something easy to do that would contribute to reduce the number of CSS files is to concatenate all the WYSIWYG CSS files from the various plugins at build time (there are more than 10 AFAIK). Marius, have you looked into this? Do you know if this could be done in the 2.1 timeframe ? Note that the target of 1 CSS and 1 JS is pretty challenging for XWiki as we are also making it a modular software where CSS and JS extensions can be conditionally loaded on some (not all) of the pages. Something to investigate for JavaScript extensions could be a dynamic JS loading mecanism, a la dojo (http://dojocampus.org/content/2008/10/09/dojo-module-packaging-and-loading/) Jerome. PS: I put devs in copy as this is more a developer topic. On 11/5/09 5:28 PM, Thibaut Camberlin wrote: > Hi all, > > Page Loading time is a very important criteria when developing a web site. > According to a recent > survey<http://www.webdesignerwall.com/general/users-place-more-weight-on-design/>more > than half people would drive away from a site with slow loading pages. > > There are several interesting issues that could be implemented to > substantially improve page loading time in XWiki. > > Number one is aggreation of CSS and JS files in order to reduce HTTP > requests. (For info, we have a total of 25 external CSS and JS files on a > basic XWiki install when in the best world we would have just 2 - 1 CSS and > 1 JS) > > Someone interrested in working on this with me ? >

15 years, 9 months

6
16
0 0

[xwiki-devs] Open Office server on myxwiki.org

by stephane barbey

Hi Team, Anybody knows if it's possible to make office document import on the myxwiki.org farm ? Thanks in advance. Stéphane Barbey.

15 years, 9 months

2
1
0 0

[xwiki-devs] Sai (pvsaikrishna@gmail.com) personally selected you to receive a Shop It To Me invite

by Sai via Shop It To Me

<p>I know you like good deals on clothing/fashion so I got you a private invitation for Shop It To Me:</p> Go here: http://www.shopittome.com/expiring_invitation/abvba9a9a1e -Sai This private invitation will expire in 24 hours. Sai (pvsaikrishna(a)gmail.com) has sent you a private invitation for Shop It To Me. If you do not want to receive these messages, paste the following link into your browser: http://www.shopittome.com/blocked_email/ZGV2c0B4d2lraS5vcmc_ Shop It To Me, Inc. 340 Brannan Street #201 San Francisco, CA 94107

15 years, 10 months

1
0
0 0

Re: [xwiki-devs] [ANN] XWiki Enterprise 2.0.4 and XWiki Enterprise Manager 2.0.4 Released

by Thomas Mortagne

It's XWiki Enterprise 2.0.4 obviously. On Fri, Nov 27, 2009 at 21:19, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote: > The XWiki development team is pleased to announce the release of XWiki > Enterprise 2.0.4 and XWiki Enterprise Manager 2.0.4. > > Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download > > This is a bug fix and enhancement release. > > Among other things it contains: > > * this time statistics are working, promise > * several important users management related issue fixed mainly > visible in path based multiwiki mode > > For more informations see the Release notes at: > http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise204 > and http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM204. > > Thanks > - The XWiki dev team > -- Thomas Mortagne

15 years, 10 months

1
0
0 0

[xwiki-devs] [ANN] XWiki Enterprise 2.0.3 and XWiki Enterprise Manager 2.0.4 Released

by Thomas Mortagne

The XWiki development team is pleased to announce the release of XWiki Enterprise 2.0.4 and XWiki Enterprise Manager 2.0.4. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This is a bug fix and enhancement release. Among other things it contains: * this time statistics are working, promise * several important users management related issue fixed mainly visible in path based multiwiki mode For more informations see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise204 and http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM204. Thanks - The XWiki dev team

15 years, 10 months

1
0
0 0

[xwiki-devs] [proposal]Add object manipulation to DocumentAccessBridge and getRenderedContent

by Anca Luca

Hi devs, in order to complete the clean implementation of the annotation features using components, I would need some API for manipulating objects from the DAB. I thought of 2 versions for it: 1/ create ObjectModelBridge interface implemented by BaseObject with: Object get(String propertyName) void set(String propertyName, Object propertyValue) int getNumber() Add to DAB: ObjectModelBridge createObject(DocumentName docName, String className) Collection<ObjectModelBridge> getObjects(DocumentName docName, String className) void removeObject(DocumentName docName, ObjectModelBridge object) void saveDocument(DocumentName docName) 2/ Add to DAB: int createObject(DocumentName docName, String className) Collection<Map<String, Object>> getObjects(DocumentName docName, String className) void setProperties(DocumentName docName, String className, int objNumber, Map<String, Object> properties) void removeObject(DocumentName docName, int objectNumber) void saveDocument(DocumentName docName) any of the two solutions is fine with me (maybe second a little more because it's minimal) WDYT? Also, since XWikiDocument.getRenderedContent() gets more and more used by various access API to XWiki (GWT, XMLRPC, etc), I propose to add to DAB: getRenderedContent(DocumentName docName, String text, Syntax sourceSyntax, Syntax finalSyntax) which would call XWikiDocument.getRenderedContent() but also xwiki.prepareResources() before so that the msg tools are initialized too (hoping this would help to programatically render a document as similar as possible with what is obtained through the view action & templates). Is there anything I'm missing from the list to achieve this? (any other setting, configuration needed, context setup, etc) Thanks, Anca

15 years, 10 months

2
2
0 0

Re: [xwiki-devs] [xwiki-notifications] r25290 - enterprise/branches/xwiki-enterprise-2.0/distribution-test/xmlrpc-tests/src/test/it/com/xpn/xwiki/it/xmlrpc enterprise/branches/xwiki-enterprise-2.0/distribution-test/xmlrpc-tests/src/test/it/org/xwiki/xmlrpc platform/core/branches/xwiki-core-2.0/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc platform/core/branches/xwiki-core-2.0/xwiki-xmlrpc/xwiki-xmlrpc-client/src/main/java/org/xwiki/xmlrpc platform/core/branches/xwiki-core-2.0/xwiki-xmlrpc/xwiki-xmlrpc-model

by Fabio Mancinelli

Hi all, I wonder if http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-xmlrpc/xwiki-x… is needed at all after the refactoring Florin did. The rationale for this interface was that before we were creating a Java proxy object in order to wrap each invocation inside a context initialization-cleanup. And since proxies could be created only by using interfaces we needed the API to be expressed as an interface. Now that the context initialization/cleanup is handled through filters there is no more need for the proxy and hence for that interface. Moreover this interface exposes method signature using XMLRPC types (so Maps instead of model objects). So it might also be confusing. I am +1 for removing it so that the code is even more clean. -Fabio On Nov 26, 2009, at 5:17 PM, tmortagne (SVN) wrote: > Author: tmortagne > Date: 2009-11-26 17:17:04 +0100 (Thu, 26 Nov 2009) > New Revision: 25290 > > Added: > enterprise/branches/xwiki-enterprise-2.0/distribution-test/xmlrpc-tests/src/test/it/org/xwiki/xmlrpc/RenderingTest.java > Modified: > enterprise/branches/xwiki-enterprise-2.0/distribution-test/xmlrpc-tests/src/test/it/com/xpn/xwiki/it/xmlrpc/AllTests.java > platform/core/branches/xwiki-core-2.0/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiXmlRpcApiImpl.java > platform/core/branches/xwiki-core-2.0/xwiki-xmlrpc/xwiki-xmlrpc-client/src/main/java/org/xwiki/xmlrpc/XWikiXmlRpcClient.java > platform/core/branches/xwiki-core-2.0/xwiki-xmlrpc/xwiki-xmlrpc-model/src/main/java/org/xwiki/xmlrpc/XWikiXmlRpcApi.java > Log: > XWIKI-4464: Extend the XmlRpc API with new rendering features > * Apply patch from Florin Ciubotaru: > ** New getRenderedContendMethods added to the api(We still need a few votes on devs for these to get commited). Completed the client with the new additions. > ** Added integration tests. > > Modified: enterprise/branches/xwiki-enterprise-2.0/distribution-test/xmlrpc-tests/src/test/it/com/xpn/xwiki/it/xmlrpc/AllTests.java > =================================================================== > --- enterprise/branches/xwiki-enterprise-2.0/distribution-test/xmlrpc-tests/src/test/it/com/xpn/xwiki/it/xmlrpc/AllTests.java 2009-11-26 15:38:04 UTC (rev 25289) > +++ enterprise/branches/xwiki-enterprise-2.0/distribution-test/xmlrpc-tests/src/test/it/com/xpn/xwiki/it/xmlrpc/AllTests.java 2009-11-26 16:17:04 UTC (rev 25290) > @@ -62,6 +62,7 @@ > addTestCase(suite, org.xwiki.xmlrpc.XWikiClassesTest.class); > addTestCase(suite, org.xwiki.xmlrpc.XWikiObjectsTest.class); > addTestCase(suite, org.xwiki.xmlrpc.SearchTest.class); > + addTestCase(suite, org.xwiki.xmlrpc.RenderingTest.class); > > return new XWikiTestSetup(suite); > } > > Copied: enterprise/branches/xwiki-enterprise-2.0/distribution-test/xmlrpc-tests/src/test/it/org/xwiki/xmlrpc/RenderingTest.java (from rev 25288, enterprise/trunk/distribution-test/xmlrpc-tests/src/test/it/org/xwiki/xmlrpc/RenderingTest.java) > =================================================================== > --- enterprise/branches/xwiki-enterprise-2.0/distribution-test/xmlrpc-tests/src/test/it/org/xwiki/xmlrpc/RenderingTest.java (rev 0) > +++ enterprise/branches/xwiki-enterprise-2.0/distribution-test/xmlrpc-tests/src/test/it/org/xwiki/xmlrpc/RenderingTest.java 2009-11-26 16:17:04 UTC (rev 25290) > @@ -0,0 +1,145 @@ > +/* > + * 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 org.xwiki.xmlrpc; > + > +import java.util.List; > + > +import junit.framework.Assert; > + > +import org.apache.xmlrpc.XmlRpcException; > +import org.xwiki.xmlrpc.model.XWikiPage; > + > +public class RenderingTest extends AbstractXWikiXmlRpcTest > +{ > + public void testGetInputSyntaxes() throws XmlRpcException > + { > + List<String> syntaxes = rpc.getInputSyntaxes(); > + > + TestUtils.banner("TEST: getInputSyntaxes()"); > + System.out.format("%d conversion input syntaxes found:\n", syntaxes.size()); > + for (String syntaxId : syntaxes) { > + System.out.format("%s\n", syntaxId); > + } > + Assert.assertTrue(syntaxes.size() != 0); > + } > + > + public void testGetOutputSyntaxes() throws XmlRpcException > + { > + List<String> syntaxes = rpc.getOutputSyntaxes(); > + > + TestUtils.banner("TEST: getOutputSyntaxes()"); > + System.out.format("%d conversion output syntaxes found:\n", syntaxes.size()); > + for (String syntaxId : syntaxes) { > + System.out.format("%s\n", syntaxId); > + } > + Assert.assertTrue(syntaxes.size() != 0); > + } > + > + public void testConvert() throws XmlRpcException > + { > + String inputXWiki = > + "**BoldText**//ItalicText//" + String.format("%n") + "==h2Text==" + String.format("%n") + "normalText"; > + String inputXhtml = > + "<div><p><strong>boldText</strong><br/><em>ItalicText</em></p>" + String.format("%n") > + + "<h2 id=\"h2Text\"><span>h2Text</span></h2><p>normalText</p></div>"; > + > + TestUtils.banner("TEST: convert()"); > + System.out.format("\nTesting xwiki/2.0 -> xhtml/1.0 conversion\n"); > + System.out.format("Input text:\n%s", inputXWiki); > + > + String outputXhtml = rpc.convert(inputXhtml, "xwiki/2.0", "xhtml/1.0"); > + > + System.out.format("\nOutput text:\n%s", outputXhtml); > + > + Assert.assertNotNull(outputXhtml); > + Assert.assertFalse(outputXhtml.equals("")); > + Assert.assertTrue(outputXhtml.contains("strong")); > + Assert.assertTrue(outputXhtml.contains("normalText")); > + Assert.assertTrue(outputXhtml.contains("ItalicText")); > + > + System.out.format("\nTesting xhtml/1.0 -> xwiki/2.0 conversion\n"); > + System.out.format("Input text:\n%s", inputXhtml); > + > + String outputXWiki = rpc.convert(inputXhtml, "xhtml/1.0", "xwiki/2.0"); > + > + System.out.format("\nOutput text:\n%s\n", outputXWiki); > + > + Assert.assertNotNull(outputXWiki); > + Assert.assertFalse(outputXhtml.equals("")); > + Assert.assertTrue(outputXhtml.contains("normalText")); > + Assert.assertTrue(outputXhtml.contains("ItalicText")); > + } > + > + public void testGetRenderedContent() throws XmlRpcException > + { > + String pageContent = "**Text in Bold**{{velocity}}VelocityCode{{/velocity}}"; > + > + XWikiPage page = new XWikiPage(); > + page.setId(TestConstants.TEST_PAGE); > + page.setContent(pageContent); > + page.setSyntaxId("xwiki/2.0"); > + > + TestUtils.banner("TEST: getRenderedContent()"); > + System.out.format("\nCalling getRenderedContent for page %s\n", page.getId()); > + System.out.format("\nWiki content is:\n%s\n", pageContent); > + > + rpc.storePage(page); > + > + try { > + String renderedContent = rpc.getRenderedContent(page.getId(), "annotatedxhtml/1.0"); > + > + System.out.format("\nObtained rendered content:\n%s\n\n", renderedContent); > + > + Assert.assertTrue(renderedContent.contains("Text in Bold")); > + Assert.assertTrue(renderedContent.contains("startmacro")); > + } finally { > + rpc.removePage(page.getId()); > + } > + } > + > + public void testRenderPageContent() throws XmlRpcException > + { > + String pageContent = "**Text in Bold**{{velocity}}VelocityCode{{/velocity}}"; > + > + XWikiPage page = new XWikiPage(); > + page.setId(TestConstants.TEST_PAGE); > + page.setContent(pageContent); > + page.setSyntaxId("xwiki/2.0"); > + > + TestUtils.banner("TEST: renderPageContent"); > + System.out.format("\nCalling renderPageContent with context as page %s\n", TestConstants.TEST_PAGE); > + System.out.format("\nWiki content is:\n%s\n", pageContent); > + > + rpc.storePage(page); > + > + try { > + String renderedContent = > + rpc.renderPageContent(page.getId(), page.getContent(), page.getSyntaxId(), "annotatedxhtml/1.0"); > + > + System.out.format("\nObtained rendered content:\n%s\n\n", renderedContent); > + > + Assert.assertTrue(renderedContent.contains("Text in Bold")); > + Assert.assertTrue(renderedContent.contains("startmacro")); > + } finally { > + rpc.removePage(page.getId()); > + } > + } > +} > > Modified: platform/core/branches/xwiki-core-2.0/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiXmlRpcApiImpl.java > =================================================================== > --- platform/core/branches/xwiki-core-2.0/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiXmlRpcApiImpl.java 2009-11-26 15:38:04 UTC (rev 25289) > +++ platform/core/branches/xwiki-core-2.0/xwiki-core/src/main/java/com/xpn/xwiki/xmlrpc/XWikiXmlRpcApiImpl.java 2009-11-26 16:17:04 UTC (rev 25290) > @@ -1446,4 +1446,47 @@ > } > return syntaxes; > } > + > + /** > + * Renders a text in the context of a wiki page. > + * > + * @param token The authentication token. > + * @param pageId The id of the page. > + * @param content The context to be rendered. > + * @param sourceSyntaxId The syntax of the content. > + * @param targetSyntaxId The target syntax of the rendered content > + * @return The rendered content. > + * @throws Exception If a invalid token is provided, an unsupported syntax id is given or the rendering fails. > + */ > + public String renderPageContent(String token, String pageId, String content, String sourceSyntaxId, > + String targetSyntaxId) throws Exception > + { > + XWikiXmlRpcUser user = XWikiUtils.checkToken(token, this.xwikiContext); > + LOG.debug(String.format("User %s has called renderPageContent()", user.getName())); > + > + Document doc = XWikiUtils.getDocument(this.xwikiApi, pageId, true); > + > + return doc.getRenderedContent(content, sourceSyntaxId, targetSyntaxId); > + } > + > + /** > + * Gets the rendered content of an existing document. > + * > + * @param token The authentication token. > + * @param pageId The id of the page. > + * @param syntaxId The target syntax of the rendered content > + * @return The rendered content > + * @throws Exception If a invalid token is provided, an unsupported syntax id is given or the rendering fails. > + */ > + public String getRenderedContent(String token, String pageId, String syntaxId) throws Exception > + { > + XWikiXmlRpcUser user = XWikiUtils.checkToken(token, this.xwikiContext); > + LOG.debug(String.format("User %s has called getRenderedContent()", user.getName())); > + > + Document doc = XWikiUtils.getDocument(this.xwikiApi, pageId, true); > + SyntaxFactory syntaxFactory = Utils.getComponent(SyntaxFactory.class); > + Syntax syntax = syntaxFactory.createSyntaxFromIdString(syntaxId); > + > + return doc.getRenderedContent(syntax); > + } > } > > Modified: platform/core/branches/xwiki-core-2.0/xwiki-xmlrpc/xwiki-xmlrpc-client/src/main/java/org/xwiki/xmlrpc/XWikiXmlRpcClient.java > =================================================================== > --- platform/core/branches/xwiki-core-2.0/xwiki-xmlrpc/xwiki-xmlrpc-client/src/main/java/org/xwiki/xmlrpc/XWikiXmlRpcClient.java 2009-11-26 15:38:04 UTC (rev 25289) > +++ platform/core/branches/xwiki-core-2.0/xwiki-xmlrpc/xwiki-xmlrpc-client/src/main/java/org/xwiki/xmlrpc/XWikiXmlRpcClient.java 2009-11-26 16:17:04 UTC (rev 25290) > @@ -932,6 +932,85 @@ > } > > /** > + * Converts a wiki source from a syntax to another syntax. > + * > + * @param source The content to be converted. > + * @param initialSyntaxId The initial syntax of the source. > + * @param targetSyntaxId The final syntax of the returned content. > + * @return The converted source. > + * @throws XmlRpcException An invalid token is provided, the syntaxId is not supported, the source is invalid or the > + * conversion fails. > + */ > + public String convert( String source, String initialSyntaxId, String targetSyntaxId) > + throws XmlRpcException > + { > + return (String) invokeRpc("convert", this.token, source, initialSyntaxId, targetSyntaxId); > + } > + > + /** > + * Gets all syntaxes supported by the rendering parsers as an input for a syntax conversion. > + * > + * @return A list containing all syntaxes supported by rendering parsers. > + * @throws Exception An invalid token is provided or the syntax lookup fails. > + */ > + public List<String> getInputSyntaxes() throws XmlRpcException > + { > + List<String> result = new ArrayList<String>(); > + Object[] objects = (Object[]) invokeRpc("getInputSyntaxes", this.token); > + for(Object object:objects) > + { > + result.add((String)object); > + } > + return result; > + } > + > + /** > + * Gets all syntaxes supported by the rendering as an output for a syntax conversion. > + * > + * @return A list containing all syntaxes supported by renderers. > + * @throws XmlRpcException An invalid token is provided or the syntax lookup fails. > + */ > + public List<String> getOutputSyntaxes() throws XmlRpcException > + { > + List<String> result = new ArrayList<String>(); > + Object[] objects = (Object[]) invokeRpc("getOutputSyntaxes", this.token); > + for(Object object:objects) > + { > + result.add((String)object); > + } > + return result; > + } > + > + /** > + * Renders a text in the context of a wiki page. > + * > + * @param pageId The id of the page. > + * @param content The contenxt to be rendered. > + * @param sourceSyntaxId The syntax of the content. > + * @param targetSyntaxId The target syntax of the rendered content > + * @return The rendered content. > + * @throws XmlRpcException If a invalid token is provided, an unsuported syntax id is given or the rendering fails. > + */ > + public String renderPageContent(String pageId, String content, String sourceSyntaxId, > + String targetSyntaxId) throws XmlRpcException > + { > + return (String) invokeRpc("renderPageContent", this.token, pageId, content, sourceSyntaxId, targetSyntaxId); > + } > + > + /** > + * Gets the rendered content of an existing document. > + * > + * @param pageId The id of the page. > + * @param syntaxId The target syntax of the rendered content > + * @return The renderded content > + * @throws Exception If a invalid token is provided, an unsuported syntax id is given or the rendering fails. > + */ > + public String getRenderedContent(String pageId, String syntaxId) throws XmlRpcException > + { > + return (String) invokeRpc("getRenderedContent", this.token, pageId, syntaxId); > + } > + > + /** > * Utility method for invoking remote RPC methods. > * > * @param methodName > > Modified: platform/core/branches/xwiki-core-2.0/xwiki-xmlrpc/xwiki-xmlrpc-model/src/main/java/org/xwiki/xmlrpc/XWikiXmlRpcApi.java > =================================================================== > --- platform/core/branches/xwiki-core-2.0/xwiki-xmlrpc/xwiki-xmlrpc-model/src/main/java/org/xwiki/xmlrpc/XWikiXmlRpcApi.java 2009-11-26 15:38:04 UTC (rev 25289) > +++ platform/core/branches/xwiki-core-2.0/xwiki-xmlrpc/xwiki-xmlrpc-model/src/main/java/org/xwiki/xmlrpc/XWikiXmlRpcApi.java 2009-11-26 16:17:04 UTC (rev 25290) > @@ -63,6 +63,11 @@ > > public String renderContent(String token, String space, String pageId, String content) throws Exception; > > + public String renderPageContent(String token, String pageId, String content, String sourceSyntaxId, > + String targetSyntaxId) throws Exception; > + > + public String getRenderedContent(String token, String pageId, String syntaxId) throws Exception; > + > public String convert(String token, String source, String initialSyntaxId, String targetSyntaxId) throws Exception; > > public List<String> getInputSyntaxes(String token) throws Exception; > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications

15 years, 10 months

2
2
0 0

[xwiki-devs] [Proposal] Component isolation implementations

by Vincent Massol

Hi, We have the need to isolate groups of components. For ex a wiki macro created in a subwiki should only be visible in that subwiki by default. Here's an implementation proposal that I'm planning to implement: * There's a Root Component Manager (the current CM) * There are 3 components which implement the ComponentManager role and with 3 hints: "wiki", "user" and "all". There's a CompositeComponentManager class that allows chaining CM and the "all" CM chains the "default" (root CM), "wiki" CM and "user" CM. This works the same as with the configuration module. * Other components can have CMs injected as they want (if not specified then it's the default, etc). For ex: @Requirement("all") private ComponentManager cm * Creation process. As for now the user creates the root CM and then the annotation loader will create the descriptors for the other CMs and register them against the root CM. They'll get instantiated once (singleton) the first time they're looked up. * In order to register a component for, say, a given "enterprise" wiki, we need to add a new property to the ComponentDescriptor: get/ setAdditionalData(Object data). For example: wikiCM.registerComponent(CD mycd) where cd.setAdditionalData("enterprise"). * Last, Guice uses Modules to isolate component definitions so it should be possible and relatively easy to port the implementation to Guice (even though Guice uses static Modules we can make them dynamic). WDYT? Thanks -Vincent

15 years, 10 months

5
17
0 0

[xwiki-devs] Fwd: [ANNOUNCE] Apache Lucene Java 3.0.0 released

by Vincent Massol

fyi -Vincent Begin forwarded message: > From: "Uwe Schindler" <uschindler(a)apache.org> > Date: November 26, 2009 10:53:40 AM CEST > To: <announce(a)apache.org>, <java-user(a)lucene.apache.org>, <java-dev(a)lucene.apache.org > > > Subject: [ANNOUNCE] Apache Lucene Java 3.0.0 released > > Hello Lucene users, > > On behalf of the Lucene dev community (a growing community far > larger than > just the committers) I would like to announce the release of Lucene > Java > 3.0.0: > > The new version is mostly a cleanup release without any new > features. All > deprecations targeted to be removed in version 3.0 were removed. If > you are > upgrading from version 2.9.1 of Lucene, you have to fix all > deprecation > warnings in your code base to be able to recompile against this > version. > > This is the first Lucene release with Java 5 as a minimum > requirement. The > API was cleaned up to make use of Java 5's generics, varargs, enums, > and > autoboxing. New users of Lucene are advised to use this version for > new > developments, because it has a clean, type safe new API. Upgrading > users can > now remove unnecessary casts and add generics to their code, too. If > you > have not upgraded your installation to Java 5, please read the file > JRE_VERSION_MIGRATION.txt (please note that this is not related only > to this > version of Lucene, it will also happen with any previous release > when you > upgrade your Java environment). > > Lucene 3.0.0 has some changes regarding compressed fields: 2.9.0 > already > deprecated compressed fields; support for them was removed now. > Lucene 3.0.0 > is still able to read indexes with compressed fields, but as soon as > merges > occur or the index is optimized, all compressed fields are > decompressed and > converted to Field.Store.YES. Because of this, indexes with compressed > fields can suddenly get larger. > > While we generally try and maintain full backwards compatibility > between > major versions, Lucene 3.0.0 has some minor breaks, mostly related to > deprecation removal, pointed out in the 'Changes in backwards > compatibility > policy' section of CHANGES.txt. Notable are: > > - IndexReader.open(Directory) now opens in read-only mode per > default (this > method was deprecated because of that in 2.9.X). The same occurs to > IndexSearcher. > > - Already started in 2.9, core TokenStreams are now made final to > enforce > the decorator pattern. > > - If you interrupt an IndexWriter merge thread, IndexWriter now > throws an > unchecked ThreadInterruptedException that extends RuntimeException and > clears the interrupt status. > > > See core changes at > http://lucene.apache.org/java/3_0_0/changes/Changes.html > and contrib changes at > http://lucene.apache.org/java/3_0_0/changes/Contrib-Changes.html > > Binary and source distributions are available at > http://www.apache.org/dyn/closer.cgi/lucene/java/ > > Lucene artifacts are also available in the Maven2 repository at > http://repo1.maven.org/maven2/org/apache/lucene/ > > > ----- > Uwe Schindler > uschindler(a)apache.org > Apache Lucene Java Committer > Bremen, Germany > http://lucene.apache.org/java/docs/ > >

15 years, 10 months

2
1
0 0

[xwiki-devs] Reduce heap exhaustion during export operation (and partly import for now)

by Denis Gervalle

Hi, As you knows, Import/Export operation on large XAR file cause problem. We felt on an even worse situation, where a single XWiki document is not properly exported due to heap exhaustion during the built of its XML DOM or due to large attachments. Having a look at the source, I have notice that many optimizations on the way the export is produce could be quite easily introduced. Currently, XWiki stored the exported document several times in memory during the operation, which impact performance negativly and is uselessly heavy on memory usage, even for reasonable documents. Therefore, I have started a large patch to avoid these caveats, here is the strategies I have followed: 1) The current implementation mostly build a DOM in memory for immediately serialized it into a stream. So I have remove the intermediate DOM and provide direct streaming of Element content by: 1.1) extending org.dom4j.XMLWriter to allow direct streaming of Element content into the output stream, as is, or Base64 encoded. Accessorily, my extension also ensure proper pairing of open/close tag. 1.2) writing a minimal DOMXMLWriter which extends my XMLWriter and could be used with the same toXML() code to build a DOMDocument to provide the toXMLDocument() methods to support the older implementation unchanged if ever needed. 1.3) using the above, minimal change to the current XML code was required 1.3.1) replacing element.add(Element) by either writer.writeElement) or writer.writeOpen(Element) 1.3.2) for large content, use my extensions, either writer.write(Element, InputStream) or writer.writeBase64(Element, InputStream) which use the InputStream for the element content 2) The current implementation for binary data such as attachments and export zip file is mostly based on in memory byte[] passing from function to function while these data initially came from a request.getInputStream() or are written to a response.getOutputStream (). So I have change these to passover the stream instead of the data: 2.1) using IOUtils.copy when required 2.2) using org.apache.commons.codec.binary.Base64OutputStream for base64 encoding when required 2.3) using an extension of ZipInputStream to cope with unexpected close() 2.4) avoid buffer duplication in favor of stream filters 3) Since most oftently used large data came from the database through an attachment content, it would be nice to have these attachment streamed from the database when they are too large. However, I feel that it is still too early to convert our binary into a blob, mainly because HSQLDB and MySQL still does not really support blob, just an emulation. These are also used to be cached in the document cache, and this will require improvement to support blob. However I propose to take the occasion to go in the direction of the blob by: 3.1) deprecating setContent(byte[]) and Byte[] getContent() in favor of newly created setContent(InputStream, int), InputStream getContentInputStream() and getSize() 3.2) Begin to use these new function as much as possible as 2) implied 3.3) this also open the ability to store attachment in another repository that support better the streaming aspect (ie: a filesystem) I am currently testing the above changes onto our client project, and I expect to provide a patch really soon. It will require an upgrade of org.apache.commons.codec to version 1.4, to have access to Base64OutputStream. I feel it will be a first step into the right direction, further improvement should be to: - import XML using a SAXParser without building a DOM in memory - manage JRCS Archive better, the way they are built and store raise the same issue then attachment - manage the recycle bin better for the same reason - improve caching to avoid caching very large stuffs WDYT ? Denis Gervalle -- SOFTEC sa http://www.softec.st

15 years, 10 months

4
5
0 0

[xwiki-devs] Regarding renaming a page

by durgaprasad karri

Hello All, I have this use case that when i rename a page it should rename the other pages with same name in the same space. ex., there are 3 pages with names "A" ,"B" and "A has / of B" in a space. when i rename "A" to say "renamedA" we need to change the other pages to" renamedA has / of B" and the same for renaming a page with name "B". I tried to catch the events when i do a rename action on the page , and there are two events fired DocumentSaveEvent and DocumentDeleteEvent and tried to apply my logic in my component to rename the pages with name in the same space but it failed . i checked the implementation of the rename method and there the object name is not changed for the renamed document because of which when i try hql query with doc.name=obj.name it fails. is there any way through which i can solve my use case? Regards Durga

15 years, 10 months

1
0
0 0

[xwiki-devs] [VOTE] Add new XWiki APIs for searching attachments (ie without programming rights)

by Vincent Massol

Hi, I'd like to apply Caleb's patch for http://jira.xwiki.org/jira/browse/XWIKI-4410 . This issue is a prereq to fix "AllDocs's attachment tab requires programming right to work" (http://jira.xwiki.org/jira/browse/XE-521). This means introducing the following new APIs: - public List<Attachment> searchAttachments(String parametrizedSqlClause, int nb, int start, List< ? > parameterValues) throws XWikiException - public List<Attachment> searchAttachments(String whereSql, int nb, int start) throws XWikiException - public List<Attachment> searchAttachments(String whereSql) throws XWikiException - public int countAttachments(String parametrizedSqlClause, List< ? > parameterValues) throws XWikiException - public int countAttachments(String whereSql) throws XWikiException Here's my +1 (even though it keeps making the class larger but I don't have any other idea for now without a huge refactoring) Thanks -Vincent

15 years, 10 months

4
3
0 0

[xwiki-devs] [VOTE] API modifications to the Rendering module to handle optional Transformations

by Vincent Massol

Hi, We have the need to handle optional Transformations (for Annotations and more generally for user-introduced annotations). Here's what Thomas and I are proposing: 1) We remove the TransformationManager component from the Rendering module (public API). This means that calling code must lookup Transformations directly. 2) We modify the Converter interface in the Rendering module in 2 ways: - add a new signature that takes a list of Transformation as parameter - modify the implementation for the signature that take no Transformation params so that no Transformations are executed when it's used (API breakage) 3) We add a XWiki configuration parameter in xwiki.properties to list the transformations that must be executed (it's a list of component hints) when a document is rendered. If this config param is not defined then the default value will contain the Macro Transformation. 4) We introduce a new module called xwiki-presentation which will contain code to handle XWiki Presentation stuff. For example: - template handling - displayers (document displayer, object displayers, etc) - display configuration - more to be defined but related to presentation The idea would be to move stuff that is currently in XWiki/ XWikiDocument related to presentation there (for example XWikiDocument.getRenderedContent could be replaced by DocumentDisplayer.display(DocumentName, Syntax, Writer output) - to be defined later). 5) In order to allow modules to not depend on xwiki-core we introduce PresentationConfiguration in the new xwiki-presentation module defined in 4) with a getViewTransformations() method corresponding to a "presentation.viewTransformations" configuration parameter. 6) We introduce a new TransformationContext class similar to MacroTransformationContext and modify the Transformation API to: void transform(XDOM, TransformationContext) (instead of XDOM dom, Syntax syntax)). TransformationContext would contain 2 type of data: - the syntax - the list of transformations being executed (this is required by some Macros. For ex the HTML macro needs it and other may need it too) 7) We remove the getPriority() method from the Transformation interface 8) We modify calling code: WYSIWYG, XMLRPC, etc to use the new Converter API and to lookup PresentationConfiguration to get access to the list of view transformations to be executed. Here's my +1 Thanks -Vincent PS: A long and complex mail... sorry about that...

15 years, 10 months

6
5
0 0

[xwiki-devs] [VOTE] Refactor rendering submodules to sort by syntax instead of by parser/renderer

by Thomas Mortagne

Hi devs, I would like to reorg a little rendering submodule on svn/maven to have: xwiki-rendering - xwiki-rendering-syntaxes -- xwiki-rendering-syntax-wikimodel -- xwiki-rendering-syntax-xml instead of the current xwiki-rendering - xwiki-rendering-parsers -- xwiki-rendering-parser-wikimodel -- xwiki-rendering-parser-xml - xwiki-rendering-renderers -- xwiki-rendering-renderer-wikimodel -- xwiki-rendering-renderer-xml Because parsers and renderer for a same syntax usually share informations and are synchronized. Here is my +1 -- Thomas Mortagne

15 years, 10 months

7
8
0 0

[xwiki-devs] [VOTE] Move XWikiContextInitializationFilter to xwiki-core

by Marius Dumitru Florea

Hi devs, I'd like to move http://svn.xwiki.org/svnroot/xwiki/platform/web/trunk/wysiwyg/src/main/java… to http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-core/src/main/… Here's my +1. Thanks, Marius

15 years, 10 months

6
7
0 0

[xwiki-devs] [VOTE] Add getRenderedContent method to xml-rpc

by Florin Ciubotaru

Hi devs, I want to add two new methods to the xml-rpc api: - String getRenderedContent(String token, String pageId, String syntaxId); - String getRenderedContent(String token, String pageId, String content, String syntaxId); Currently we are only able to get xhtml/1.0 output by using getPage and accesing page.Content from the methods output. We need this new methods to get the output in different syntaxes(Eg: annotatedxhtml). This is useful to parse the output for macros, images and links like we do in the wysiwyg. I'd like the code to go in the 2.0.4 release. The old method invocation required different method names. Since we don't have the xml-rpc cleanup in 2.0.4 we probably need to have different naming for the methods above. Since starting with 2.1 we use the Apache Xml-Rpc method lookup and invocation, we might be able to use the same name and different signature in the future. I'll need to check this. WDYT? Thanks, Florin Ciubotaru

15 years, 10 months

4
3
0 0

Re: [xwiki-devs] Automatic update

by MOUZELER Cyril

For Hibernate.cfg.xml it is ok but when i upgrade from 1.9.3 to 2.0.3 I got a crash when I copied the entire xwiki.cfg. Regarding my script modifications : I change in login.vm (in colibri skin) the message regarding the forgotten message like follow : ## TODO: Replace this with an interface extension once IX are implemented #if($xwiki.exists("XWiki.ResetPassword")) ## <div style="font-size: 70%; margin-top: 2em;">Forgot your <a href="$xwiki.getURL('XWiki.ForgotUsername')">username</a> or <a href="$xwiki.getURL('XWiki.ResetPassword')">password</a>?</div> <div style="font-size: 70%;font-style:bold;color:#005A83; margin-top: 2em;">To connect, use your Network Id and password.</div> #end In a future, I hope to implement SSO...and then avoid such modification ;-) Cyril -----Message d'origine----- De : devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] De la part de Vincent Massol Envoyé : mercredi 25 novembre 2009 12:23 À : XWiki Developers Objet : Re: [xwiki-devs] Automatic update On Nov 25, 2009, at 12:10 PM, MOUZELER Cyril wrote: > Currently this is my process: > > 1. download the XEM war > 2. unzip the file into my jetyt/webapps folder 3. configure > hibernate.cfg.xml This one is not needed. You can simply reuse your existing config file. > 4. in the xwiki.cfg set the ldap part(server, user, group), the stat > part, virtual part, lucene part Again this one is not needed you can reuse your existing file. > 5. in the xwiki.properties set OpenOffice part Same as above. > 6. in the xwiki itself , set the Alias for default name, the smtp > server. Again not needed. You just need to not import XWikiPreferences. Or are you talking about another page? > 7. adjust some skins modifications, script modifications. Any details on these? > Several times I tryed to copy directly the file but I got a crash > (some properties in hybernate file change, new properties definition > in the xwiki.cfg...). hmm... What you could do is a diff between your version and the new version. In general whatever new config param we add has a default value that is similar to the old behavior so it shouldn't change anything. Personally I'd like to move all config files in a .xwiki directory in your user directory so that upgrades don't require you to remember to save your config and put it back. > Points 4 to 7 consume time. > I understand that the automatic process is complex (for example to > change the script...) I will have a look on the ExtensionManager. IMO the only real hard part is the upgrade of the XAR (ie the wiki pages). To reduce this burden you should try to not change pages packaged in the default XAR and instead create new pages. This will prevent you from overwriting changes. There's also a list of page you should not upgrade, listed in the Installation guide. It's for the XAR upgrade that we'd like to have the Extension Manager in the future. Thanks -Vincent > Thx for your answer ! > > Cyril > > -----Message d'origine----- > De : devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] De la part > de Vincent Massol Envoyé : mercredi 25 novembre 2009 11:49 À : XWiki > Developers Objet : Re: [xwiki-devs] Automatic update > > Hi Cyril, > > On Nov 25, 2009, at 11:39 AM, MOUZELER Cyril wrote: > >> Hi all, >> >> Is it planned to develop a way to update xwiki automatically ? >> I have installed XEM on Windows using Oracle, ActiveDirectory, >> Exchange, Openoffice... To configure all, it takes time and it is not >> an obvious task. > > Could you list the tasks that take time? (I have some idea but would > be interested to know what you think is painful in the upgrade > process). > > Note: In the future we've planned to implement an extension manager, > see http://dev.xwiki.org/xwiki/bin/view/Design/ExtensionManager > > Thanks > -Vincent > >> That's why i am wondering if there is a way to automatically update >> XEM without change the conf. >> >> >> >> Cyril > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > ---------------------------------------------------------------------- > ---------- > > This e-mail is intended only for the addressee named above. It does > not bind the sender, except in the case of an existing written > convention with the addressee. This e-mail may contain material that > is confidential and privileged for the sole use of the intended > recipient. Any review, reliance or distribution by others or > forwarding without express permission is strictly prohibited and may > be unlawful. If you are not the intended recipient, please contact the > sender and delete all copies. > > While reasonable precautions have been taken to ensure that this e- > mail and any attachments are free from any computer virus or similar > defect, no liability will be accepted in that respect. Anyone > accessing this e-mail must take their own precautions as to security > and virus protection. > > KBL European Private Bankers S.A., 43 boulevard Royal L-2955 > Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1 > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs -------------------------------------------------------------------------------- This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies. While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection. KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1

15 years, 10 months

2
1
0 0

Re: [xwiki-devs] [xwiki-notifications] r25282 - enterprise/trunk

by Jean-Vincent Drean

Sorry about that, I'm struggling with subversive. JV. On Wed, Nov 25, 2009 at 1:24 PM, jvdrean <enterprise-notifications(a)xwiki.org> wrote: > Author: jvdrean > Date: 2009-11-25 13:24:14 +0100 (Wed, 25 Nov 2009) > New Revision: 25282 > > Added: > enterprise/trunk/xwiki-enterprise-parent/ > Log: > Share project "xwiki-enterprise-parent" into "http://svn.xwiki.org/svnroot/xwiki/enterprise/trunk/distribution-test/misc-…" > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications >

15 years, 10 months

1
0
0 0

Re: [xwiki-devs] Automatic update

by MOUZELER Cyril

Currently this is my process: 1. download the XEM war 2. unzip the file into my jetyt/webapps folder 3. configure hibernate.cfg.xml 4. in the xwiki.cfg set the ldap part(server, user, group), the stat part, virtual part, lucene part 5. in the xwiki.properties set OpenOffice part 6. in the xwiki itself , set the Alias for default name, the smtp server. 7. adjust some skins modifications, script modifications. Several times I tryed to copy directly the file but I got a crash (some properties in hybernate file change, new properties definition in the xwiki.cfg...). Points 4 to 7 consume time. I understand that the automatic process is complex (for example to change the script...) I will have a look on the ExtensionManager. Thx for your answer ! Cyril -----Message d'origine----- De : devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] De la part de Vincent Massol Envoyé : mercredi 25 novembre 2009 11:49 À : XWiki Developers Objet : Re: [xwiki-devs] Automatic update Hi Cyril, On Nov 25, 2009, at 11:39 AM, MOUZELER Cyril wrote: > Hi all, > > Is it planned to develop a way to update xwiki automatically ? > I have installed XEM on Windows using Oracle, ActiveDirectory, > Exchange, Openoffice... To configure all, it takes time and it is not > an obvious task. Could you list the tasks that take time? (I have some idea but would be interested to know what you think is painful in the upgrade process). Note: In the future we've planned to implement an extension manager, see http://dev.xwiki.org/xwiki/bin/view/Design/ExtensionManager Thanks -Vincent > That's why i am wondering if there is a way to automatically update > XEM without change the conf. > > > > Cyril _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs -------------------------------------------------------------------------------- This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies. While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection. KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1

15 years, 10 months

2
1
0 0

[xwiki-devs] Automatic update

by MOUZELER Cyril

Hi all, Is it planned to develop a way to update xwiki automatically ? I have installed XEM on Windows using Oracle, ActiveDirectory, Exchange, Openoffice... To configure all, it takes time and it is not an obvious task. That's why i am wondering if there is a way to automatically update XEM without change the conf. Cyril -------------------------------------------------------------------------------- This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies. While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection. KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1

15 years, 10 months

3
2
0 0

[xwiki-devs] [vote] move the annotations plugin / application from the sandbox to platform

by Anca Luca

Hello devs, as a result of the cleaning of the annotations extension, I propose to move it to the platform xwiki-plugins and the respective xwiki-applications. The application (client) could use a little more stabilization, but I prefer to do it when I get to the client improvements part, as presented in the last roadmap at http://markmail.org/message/5mnfhpdf2cgqlbop (at the end of mail). I would like to do that now since what we have now is runnable, somewhat usable, it represents a clean, correct version of what we have in the sandbox, a "zero point". I am starting to make improvements from here on. WDYT? Thanks, Anca

15 years, 10 months

5
6
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs