xwiki-devs July 2010

xwiki-devs@xwiki.org

30 participants
45 discussions

[xwiki-devs] Fwd: Need advice before issuing a new wiki request on myxwiki.org

by Bogdan Flueras

Hello Xwiki Devs, I plan to create a new wiki on myxwiki.org for a large comunity of non-technical users (~1K), so Xwiki is my first choice. However I will add new features to the wiki, like: OpenId and JForum, so what I'm asking if there is a possibility to RE-deploy my modified webapp onto myxwiki.org afterwards, OR once the created wiki there is no other possibility to improve it ... If the answer would be yes, I would be grateful for a How-To. If not, I would search for dedicated hosting, and still be grateful for your work! Best regards! --

14 years, 1 month

[xwiki-devs] [Proposal] Introduce automated escaping tests

by Alex Busenius

Hello devs, I'd like to add a new test framework aimed on catching XML escaping bugs that we currently have almost everywhere. Escaping bugs cause broken, unusable pages when special characters are used in space/page/category/user/whatever names and often present serious security issues. This test framework will run automatic tests and also allow for writing manual tests. Currently, escaping tests are usually written using selenium2, see e.g.: http://svn.xwiki.org/svnroot/xwiki/enterprise/trunk/distribution-test/ui-te… This is a bad solution, slow and tricky to write. Writing unit tests for such bugs is also not a good solution, because most of the time they originate in velocity templates. It is hard to test a single template in isolation, they usually require access to many API functions. The solution I propose works similar to webstandards tests. The framework searches for all templates and documents in XWiki Enterprise *.xar and *.war and generates automatic escaping tests for each of them. Each test then requests URLs from XWiki server with different parameters and runs a custom validator that searches for not escaped data in the response. Manual tests can also be added easily. The implementation can be found in the sandbox: https://svn.xwiki.org/svnroot/xwiki/contrib/sandbox/xwiki-enterprise-test-e… It currently implements some simple automated escaping tests on all templates and applications from the XAR. The parameters to use are chosen based on the source, using matching with regular expressions (searches for things like $request.get("something")). Full test run takes 8 minutes on my laptop. Current results: Tests run: 499, Failures: 166, Errors: 3, Skipped: 0 (there are still some false positives that I need to track down though). Files and test classes can be excluded from the tests using various properties set in maven (see pom.xml). Usual -Dtest and -Dpattern are also supported, e.g. to test all pages from "Blog" space, run: mvn -Dtest=ApplicationTest -Dpattern='^Blog/' install Some implementation details: org.xwiki.escaping.suite It is a custom JUnit4 test suite. It reads given zip file, then creates and initializes instances of the test class for each found file. The test class must implement FileTest (defines initialize()) and annotated with @RunWith(ArchiveSuite.class). Test classes can decide based on file name and content whether they can test the given file or not. ApplicationTest and TemplateTest use this suite. org.xwiki.escaping.framework Contains base classes for the escaping tests (implement downloading data from server, regex-based "parsing" etc.), escaping validator etc. org.xwiki.escaping Contains the tests (2 automatic and 1 manual). Instances of the test classes (built by ArchiveSuite or manual ones) a run using the default JUnit4 test runner, so all fancy test method annotations are supported. I propose to add this test framework to the main repository starting with 2.5 branch. This will give us more time to fix current issues (problematic files can be easily excluded to generate less noise). WDYT? Regards, Alex

14 years, 1 month

[xwiki-devs] How to get all versions of an attachment via XML-RPC?

by Wolfgang Philipp

Hello, we are developing an application which uses the XML-RPC API of XWiki. It is the only way to get to the data stored in the wiki in our case (except DB access, which we want to avoid in first place). In our data model there is a media entity which serves as a container for the revisions of this given media entity. That means I need all the versions of an attachment, not just the current/latest version. I do not see a way to get to these data via the XML-RPC client interface. Is there a way to get all the versions of an attachment? And if so, is there also a way to determine the version number of a given attachment? Thx in advance for your answers!

14 years, 1 month

[xwiki-devs] [Announcement] XWiki Enterprise 2.4 and XWiki Enterprise Manager 2.4 Released

by Sergiu Dumitriu

The XWiki development team is pleased to announce the release of XWiki Enterprise and XWiki Enterprise Manager 2.4. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download The highlights of this release are a new template-based page creation, invitations, object and class editor improvements (especially the ability to remove class properties), and several security and performance improvements. Important changes since XWiki Enterprise 2.3.2: * Changed the default search engine from the direct database search to Lucene, plus a new section in the Administration page for managing the search engine * New template based page creation, which allows to define templates for new pages * A new Invitation Manager application, which allows users to invite other people to join the wiki * The ability to insert external images in the WYSIWYG editor * One-click paste button in the WYSIWYG toolbar * The ability to add one-click buttons for inserting certain macros * The ability to delete and to disable/re-enable class properties * Usability improvements for the object and class editors * Usability improvements for the Watchlist * Faster page loading using defered scripts * Many fixes against Cross-Site Scripting attacks * Many other bug fixes For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/Main/ReleaseNotesXWikiEnterprise24 and http://www.xwiki.org/xwiki/bin/Main/ReleaseNotesXEM24 Thanks -The XWiki dev team -- Sergiu Dumitriu http://purl.org/net/sergiu/

14 years, 1 month

[xwiki-devs] XWiki Rendering outside XWiki in a standalone project

by Farrukh Ijaz

Hi Everyone, I am novice to XWiki. I want to use XWiki standalone rendering module outside XWiki. I followed the instructions on the following page. http://code.xwiki.org/xwiki/bin/view/Modules/RenderingModule I've configured a project in NetBeans IDE and included following JAR to the classpath. xwiki-core-rendering-standalone-2.2.4.jar Here is the hello world example: package xwikitest; import java.io.StringReader; import java.util.logging.Level; import java.util.logging.Logger; import org.xwiki.component.embed.EmbeddableComponentManager; import org.xwiki.rendering.converter.Converter; import org.xwiki.rendering.renderer.printer.*; import org.xwiki.rendering.syntax.Syntax; public class HelloWorld { public static void main(String[] args) { new HelloWorld().sayHello(); } public void sayHello() { EmbeddableComponentManager ecm = new EmbeddableComponentManager(); ecm.initialize(this.getClass().getClassLoader()); WikiPrinter printer = new DefaultWikiPrinter(); Converter converter; try { converter = ecm.lookup(Converter.class); converter.convert(new StringReader("Hello **World**"), Syntax.MEDIAWIKI_1_0, Syntax.XHTML_1_0, printer); System.out.println(printer.toString()); } catch (Exception ex) { Logger.getLogger(HelloWorld.class.getName()).log(Level.SEVERE, null, ex); } } } But it's raising following exception at line ecm.initialize(this.getClass().getClassLoader()); Exception in thread "main" java.lang.RuntimeException: Failed to dynamically load components with annotations at org.xwiki.component.annotation.ComponentAnnotationLoader.initialize(ComponentAnnotationLoader.java:136) at org.xwiki.component.embed.EmbeddableComponentManager.initialize(EmbeddableComponentManager.java:69) at xwikitest.Main.test(Main.java:32) at xwikitest.Main.main(Main.java:27) Caused by: java.lang.ClassNotFoundException: at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:315) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:330) at java.lang.ClassLoader.loadClass(ClassLoader.java:250) at org.xwiki.component.annotation.ComponentAnnotationLoader.initialize(ComponentAnnotationLoader.java:97) ... 3 more Java Result: 1 Am I missing any other jar(s)? Any prompt help will be highly appreciated. Farrukh

14 years, 1 month

[xwiki-devs] Fwd: The Apache Software Foundation Announces Apache FOP Version 1.0

by Sergiu Dumitriu

FYI -------- Original Message -------- Subject: The Apache Software Foundation Announces Apache FOP Version 1.0 Date: Wed, 21 Jul 2010 19:39:47 +0200 From: Simon Pepping <spepping(a)leverkruid.eu> Reply-To: fop-users(a)xmlgraphics.apache.org To: fop-dev(a)xmlgraphics.apache.org <fop-dev(a)xmlgraphics.apache.org>, fop-users(a)xmlgraphics.apache.org <fop-users(a)xmlgraphics.apache.org>, general(a)xmlgraphics.apache.org <general(a)xmlgraphics.apache.org>, general(a)xml.apache.org Redesigned, Stable Version of Pioneering XSL Formatting Objects Processor Rounds Out Apache XML Software Stack FOREST HILL, Md., July 21 -- The Apache Software Foundation (ASF) - the all-volunteer developers, stewards, and incubators of nearly 150 Open Source projects and initiatives - today announced the Version 1.0 release of Apache FOP, the Open Source XSL Formatting Objects Processor. An Apache project since 1999, FOP is one of the industry's first print formatters driven by W3C-standard XSL Formatting Objects created to display, convert, and print to formats such as PDF, PostScript, SVG, RTF, and XML. In addition, FOP is among the most commonly-used output-independent formatters. The Apache FOP code base has grown over the past decade under the guidance of a Project Management Committee (PMC) who oversee its day-to-day activities and community development. "FOP v.1.0 provides a good subset of the W3C XSL-FO 1.0/1.1 specification. Its stable, 1.0 designation provides added recognition as the productive tool it has been for years," said Jeremias Marki, member of the Apache XML Graphics Project Management Committee. "Its redesign and improved features in the layout engine makes it an even better experience for the many developers and users who produce millions of pages each year." Apache FOP is in use at Accenture, Airbus, Australia Post, BNP Paribas, Capgemini, Credit Suisse, CSC, Denic, European Patent Office, FedEx, Ford, HP, IBM, IntelliData, Marriot International, Morgan Stanley, Polaris, Siemens, Swiss Federal Institute of Intellectual Property, Tecra, US Army, US House of Representatives, and Wyona, among many others. In addition, FOP is the default implementation bundled in XML editors such as XSLfast, Oxygen, and XMLSpy. "Thunderhead relies on open standards, and FOP is at the heart of our innovative NOW platform. We are proud to have been able to play a part in its development," said Glen Manchester, CEO of Thunderhead. "As long-time supporters of FOP, our congratulations go to the whole FOP team at Apache on reaching the Version 1.0 milestone." The release of FOP v.1.0 completes a free XML software stack, comprising: Apache Xerces, Apache Xalan, and Apache FOP. The ability to insert graphics into one's print output is possible using Apache Batik. The Apache XML stack makes transforming and formatting XML data (for example DocBook XML) a viable option for individual and start-up users without business cash flow. "Some 'overnight successes' take ten years or more," said James Governor, Analyst and Founder of RedMonk. "Apache FOP seems to be one of them." "The training wheels are long gone," said Apache XML Graphics PMC Chair Simon Pepping. "FOP's popularity is undisputed; FOP is used from an individual developer's pet project to large-scale document production. FOP is not yet 'feature complete', and work on it is continuing. We hope this important step forward will motivate skilled developers to jump in and help us make Apache FOP even better." Availability FOP v.1.0 is released under the Apache Software License v2.0. Downloads, documentation, and related resources are available at http://xmlgraphics.apache.org/fop/. -- Simon Pepping home page: http://www.leverkruid.eu --------------------------------------------------------------------- To unsubscribe, e-mail: fop-users-unsubscribe(a)xmlgraphics.apache.org For additional commands, e-mail: fop-users-help(a)xmlgraphics.apache.org

14 years, 1 month

Re: [xwiki-devs] [xwiki-notifications] r30303 - platform/web/trunk

by Sergiu Dumitriu

On 07/20/2010 10:14 AM, Jerome Velociter wrote: > > ----- "sdumitriu (SVN)"<platform-notifications(a)xwiki.org> wrote: > >> Author: sdumitriu >> Date: 2010-07-16 23:05:05 +0200 (Fri, 16 Jul 2010) >> New Revision: 30303 >> >> Modified: >> platform/web/trunk/pom.xml >> Log: >> [release] Updated dependencies after branch >> >> Modified: platform/web/trunk/pom.xml >> =================================================================== >> --- platform/web/trunk/pom.xml 2010-07-16 20:53:36 UTC (rev 30302) >> +++ platform/web/trunk/pom.xml 2010-07-16 21:05:05 UTC (rev 30303) >> @@ -50,7 +50,7 @@ >> <junit.version>3.8.2</junit.version> >>  >> >> <platform.tool.configuration.version>1.43-SNAPSHOT</platform.tool.configuration.version> >> -<platform.core.version>2.4-SNAPSHOT</platform.core.version> >> +<platform.core.version>${pom.version}</platform.core.version> > > Shouln't we start using ${project.version} instead ? > > (pom.* will be deprecated in Maven 3) Yep, we should. -- Sergiu Dumitriu http://purl.org/net/sergiu/

14 years, 1 month

[xwiki-devs] [VOTE] Release 2.4 final

by Sergiu Dumitriu

Hi devs, The 2.4 release was planned for yesterday, but since the 2.4 release manager is unavailable, and we didn't decide on a replacement in time, I'd like to do the 2.4 release as soon as possible, after I fix the remaining failing tests. -- Sergiu Dumitriu http://purl.org/net/sergiu/

14 years, 1 month

Re: [xwiki-devs] [xwiki-notifications] r30338 - platform/skins/trunk/colibri/src/main/resources/colibri

by Caleb James DeLisle

sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2010-07-18 17:33:08 +0200 (Sun, 18 Jul 2010) > New Revision: 30338 > > Modified: > platform/skins/trunk/colibri/src/main/resources/colibri/editinline.vm > Log: > [cleanup] Updated deprecated method calls > > Modified: platform/skins/trunk/colibri/src/main/resources/colibri/editinline.vm > =================================================================== > --- platform/skins/trunk/colibri/src/main/resources/colibri/editinline.vm 2010-07-18 15:32:58 UTC (rev 30337) > +++ platform/skins/trunk/colibri/src/main/resources/colibri/editinline.vm 2010-07-18 15:33:08 UTC (rev 30338) > @@ -47,10 +47,10 @@ > <input type="hidden" name="template" value="$!request.template" /> > <input type="hidden" name="language" value="$!doc.language" /> > #if("$!request.parent" != '') > - <input type="hidden" name="parent" value="$xwiki.getXMLEncoded($!request.parent)" /> > + <input type="hidden" name="parent" value="$escapetool.html($!request.parent)" /> Is it supposed to be $escapetool.html( or $escapetool.xml(? I had been using html until I saw you using xml and switched to xml. Which one should we be using? Caleb > #end > #if("$!request.title" != '') > - <input type="hidden" name="title" value="$xwiki.getXMLEncoded($!request.title)" /> > + <input type="hidden" name="title" value="$escapetool.html($!request.title)" /> > #end > ## ---------------------------- > ## Display the rendered content > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications >

14 years, 1 month

[xwiki-devs] [Proposal] [Vote] User Avatars

by Ecaterina Valica

Hi, I've made a proposal about the usage of user avatars. http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AvatarsProposal Primary usage of avatars should have a 50x50px image, while secondary/lower importance usage should have 30x30px image. Please *vote *if you agree with this sizes. I've integrates avatars with: -* Comments* http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AvatarsProposalCom… Please *vote *if you agree with this changes -* Annotations* (also did a restyling to be more consistent) http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AvatarsProposalAnn… Please *vote *if you agree with this changes - *Other* http://incubator.myxwiki.org/xwiki/bin/view/Improvements/AvatarsProposalDas… All feedback is welcomed. Thanks, Caty

14 years, 1 month

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs July 2010