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

Re: [xwiki-devs] [xwiki-notifications] XWiki updates, 2, 077 documents have been modified since 2012/01/30
by Thomas Mortagne 31 Jan '12

31 Jan '12

On Tue, Jan 31, 2012 at 12:01 AM, <watchlist(a)xwiki.org> wrote: > Error number 4001 in 4: Error while parsing velocity page > xwiki:XWiki.WatchListMessage Wrapped Exception: Failed to evaluate content > with id [xwiki:XWiki.WatchListMessage] > > Error number 4001 in 4: Error while parsing velocity page > xwiki:XWiki.WatchListMessage > Wrapped Exception: Failed to evaluate content with id > [xwiki:XWiki.WatchListMessage] > com.xpn.xwiki.XWikiException: Error number 4001 in 4: Error while parsing > velocity page xwiki:XWiki.WatchListMessage > Wrapped Exception: Failed to evaluate content with id > [xwiki:XWiki.WatchListMessage] > at > com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:122) > at > com.xpn.xwiki.plugin.mailsender.MailSenderPlugin.sendMailFromTemplate(MailSenderPlugin.java:813) > at > com.xpn.xwiki.plugin.watchlist.WatchListNotifier.sendEmailNotification(WatchListNotifier.java:133) > at > com.xpn.xwiki.plugin.watchlist.WatchListJob.executeJob(WatchListJob.java:270) > at com.xpn.xwiki.plugin.scheduler.AbstractJob.execute(AbstractJob.java:71) > at org.quartz.core.JobRunShell.run(JobRunShell.java:202) > at > org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525) > Caused by: org.xwiki.velocity.XWikiVelocityException: Failed to evaluate > content with id [xwiki:XWiki.WatchListMessage] > at > org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:247) > at > org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:184) > at > com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:117) > ... 6 more > Caused by: org.apache.velocity.exception.MethodInvocationException: > Invocation of method 'getHTMLDiff' in class > com.xpn.xwiki.plugin.watchlist.WatchListEvent threw exception > java.lang.NullPointerException at xwiki:XWiki.WatchListMessage[line 148, > column 33] > at > org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:243) > at > org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:187) > at > org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280) > at org.apache.velocity.context.ProxyVMContext.get(ProxyVMContext.java:219) > at > org.apache.velocity.runtime.parser.node.ASTReference.getVariableValue(ASTReference.java:991) > at > org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:240) > at > org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:567) > at > org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71) > at > org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142) > at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) > at > org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:216) > at > org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:311) > at > org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:230) > at > org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:207) > at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) > at > org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87) > at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) > at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:420) > at > org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:207) > at > org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342) > at > org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:228) > ... 8 more > Caused by: java.lang.NullPointerException > at com.xpn.xwiki.objects.BaseProperty.equals(BaseProperty.java:108) > at com.xpn.xwiki.objects.NumberProperty.equals(NumberProperty.java:57) > at com.xpn.xwiki.objects.BaseCollection.equals(BaseCollection.java:624) > at com.xpn.xwiki.objects.classes.BaseClass.getDiff(BaseClass.java:1211) > at com.xpn.xwiki.doc.XWikiDocument.getClassDiff(XWikiDocument.java:5600) > at > com.xpn.xwiki.plugin.watchlist.WatchListEvent.getHTMLDiff(WatchListEvent.java:534) > at sun.reflect.GeneratedMethodAccessor706.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:395) > at > org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:384) > at > org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:173) > ... 27 more > > > Wrapped Exception: > > org.apache.velocity.exception.MethodInvocationException: Invocation of > method 'getHTMLDiff' in class com.xpn.xwiki.plugin.watchlist.WatchListEvent > threw exception java.lang.NullPointerException at > xwiki:XWiki.WatchListMessage[line 148, column 33] > at > org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:243) > at > org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:187) > at > org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:280) > at org.apache.velocity.context.ProxyVMContext.get(ProxyVMContext.java:219) > at > org.apache.velocity.runtime.parser.node.ASTReference.getVariableValue(ASTReference.java:991) > at > org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:240) > at > org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:567) > at > org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:71) > at > org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:142) > at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) > at > org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:216) > at > org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:311) > at > org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:230) > at > org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:207) > at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) > at > org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87) > at > org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72) > at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:420) > at > org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:207) > at > org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:342) > at > org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:228) > at > org.xwiki.velocity.internal.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:184) > at > com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:117) > at > com.xpn.xwiki.plugin.mailsender.MailSenderPlugin.sendMailFromTemplate(MailSenderPlugin.java:813) > at > com.xpn.xwiki.plugin.watchlist.WatchListNotifier.sendEmailNotification(WatchListNotifier.java:133) > at > com.xpn.xwiki.plugin.watchlist.WatchListJob.executeJob(WatchListJob.java:270) > at com.xpn.xwiki.plugin.scheduler.AbstractJob.execute(AbstractJob.java:71) > at org.quartz.core.JobRunShell.run(JobRunShell.java:202) > at > org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:525) > Caused by: java.lang.NullPointerException > at com.xpn.xwiki.objects.BaseProperty.equals(BaseProperty.java:108) > at com.xpn.xwiki.objects.NumberProperty.equals(NumberProperty.java:57) > at com.xpn.xwiki.objects.BaseCollection.equals(BaseCollection.java:624) > at com.xpn.xwiki.objects.classes.BaseClass.getDiff(BaseClass.java:1211) > at com.xpn.xwiki.doc.XWikiDocument.getClassDiff(XWikiDocument.java:5600) > at > com.xpn.xwiki.plugin.watchlist.WatchListEvent.getHTMLDiff(WatchListEvent.java:534) > at sun.reflect.GeneratedMethodAccessor706.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:395) > at > org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:384) > at > org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:173) > ... 27 more > > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications > A pity we don't have the document and the compared version or at least the field name in the log. According to the error, some property class has a new number field compared to 3.1.1. Does this sounds expected to anyone ? -- Thomas Mortagne

1 2

[xwiki-devs] a page-sources project?
by Paul Libbrecht 30 Jan '12

30 Jan '12

Hello fellow XWikiers, I am regularly working with my favorite IDE, IntelliJ IDEA, and it is doing a very good work for me to edit velocity and groovy. I am using this also for the source of wiki pages which I upload using a tiny upload script (that posts like a form using curl and simple preemptive authentication, [1]). The interest of storing page-sources as files is that you get all the IDE services (it could work with most IDEs) such as auto-completion, code-usage-tracking, or html and javascript validation. The other interest is that my source files enter versioning. I can commit these so that I and other developers know it's part of the build for the future, independently of my server upload and developer readable in versioning system. Thus far I've been using wiki/src/main/pages/<spaceName>/<pageName>.vm (or .grv, .properties, ...). There's a single issue I stumble across: for IntelliJ to do me classpath resolution (e.g. recognize an import for the Context class), I need to change the maven project type from xar to jar. And this is not so good. My next step would thus be to create a new sub-project, xwikipages, containing these pages... but maybe everything is wrong here. My questions: • how much of that is good or best practice? • what do others use as IDE-exploitation for XWiki-pages? (XEclipse and the Git xwiki-application?) • is anyone else interested into sharing such a practice and enhance it commonly? thanks in advance Paul [1] upload-to-wiki can be found in https://github.com/xwiki-contrib/xwiki-clams-core/tree/master/tools/src/mai…

4 6

[xwiki-devs] [Proposal] Use liquibase to manage the database schema
by Denis Gervalle 29 Jan '12

29 Jan '12

While trying to reduce the likelihood of duplicate ids for documents, and extending my patch to provide a proper solution for objects, I fall on a really unexpected issue: the type of the object identifiers are Integer where those of documents are Long. This is completely abnormal since we have several objects per documents, and therefore we need more distinct ids for objects than documents. I have therefore upgraded the ids of objects to use Long, and provide an implementation that use the lowest 64bits of an MD5 key for object in the same way I do for documents. This implementation introduce two new serializer: UidStringEntityReferenceSerializer and LocalUidStringEntityReferenceSerializer. I have also bridged the statistics that derived from objects. The new implementation works perfectly on a new database but... ... I am unable to provide a proper migration procedure, since hibernate cannot manage changing the types of existing columns. It does not complains during schema update, it simply do nothing about them. And later the data migration breaks since my hashes cannot fit in the database properly. After thorough googling, I understand that hibernate schema updates were not made for production use and are really limited opposed to the general idea we had of it. Since I am currently stucked, I propose to move ahead and use a new tool to properly manage our database schema upgrade: http://www.liquibase.org/ Liquibase is Apache licensed and provide a database agnostic version system for migrating databases. It does not works like a diff tool, but more like a patch tool, where you provide several XML description of your wanted changes and it manage to apply or rollback there changes in an ordered manner to upgrade the database to the latest schema. There is several way to apply these changes and I would like to see if it could be integrated in our current migration procedure, or at least as an independent listener. WDYT ? -- Denis Gervalle SOFTEC sa - CEO eGuilde sarl - CTO

3 4

[xwiki-devs] [Vote] Dates for 3.5 release
by Marius Dumitru Florea 27 Jan '12

27 Jan '12

Hi devs, In a previous mail I proposed the following dates for 3.5: 3.5RC1: 6 February (2 weeks) 3.5Final: 13 February (1 week) As you can see I haven't included a milestone because the initial plan was to do only bug fixes as 3.5 is the last release of the 3.x cycle. It seems though that we're going to introduce new stuff and improvements (for Extension Manager and App Within Minutes at least) and thus a milestone is now needed. Thus I propose these new dates: 3.5M1: 6 February (2 weeks) 3.5RC1: 13 February (1 week) 3.5Final: 20 February (1 week) WDYT? Thanks, Marius

6 5

[xwiki-devs] XAR Import Ant Task
by Richard Hierlmeier 26 Jan '12

26 Jan '12

Hi Developers, I implement an ant task that allows the import of xar files into a xwiki database. This Tasks uses a class that is derived from AbstractPackager. Whenever an object of this class calls AbstractPackager.createXWikiContext I get an exception with the following root cause: Caused by: java.lang.NullPointerException at org.xwiki.context.internal.DefaultExecutionContextManager.initialize(DefaultExecutionContextManager.java:138) at com.xpn.xwiki.tool.backup.AbstractPackager.createXWikiContext(AbstractPackager.java:75) at ... It seems that this AbstractPackager.createXWikiContext method works only on some circumstances. I assume that the injection mechanism is not working in my case. In a seconds test I implemented a main method in the AntTask, and provided the parameter via command line. And it worked but only under the condition that the required classpath is defined in the manifest of the jar and the program is started via java -jar xarImportAntTask.jar When I setup the classpath externally and start it with java -cp ... de.hierlmeier.xwiki.ant.XarImportTask I get the same NullPointerException as within ant. Can someone give me a hint to solve the problem? If anyone is interrested I can contribute the ant task to the open source community (once it is working). Here is a sample ant configuration: <taskdef name="importXar" classname="de.hierlmeier.xwiki.ant.XarImportTask"> <classpath> <pathelement location="${instdir}/xwiki/WEB-INF"/> <pathelement location="${instdir}/xwiki/WEB-INF/classes"/> <fileset dir="${instdir}/xwiki/WEB-INF/lib"> <include name="*.jar"/> </fileset> </classpath> </taskdef> <importXar hibernateConfig="${instdir}/xwiki/WEB-INF/hibernate.cfg.xml" xwikidb="xwiki"> <xarFiles dir="${basedir}/xars"> <include name="*.xar"/> </xarFiles> </importXar> Thank you in advance Richard

1 0

[xwiki-devs] [VOTE] Create Committers list for internal committers stuff + use it for collecting poll results
by Vincent Massol 26 Jan '12

26 Jan '12

Hi devs, We had already discussed the creation of a committers list earlier, see http://markmail.org/thread/bnimte63t3tojslz I'd like to revive this topic in view of a new use case: poll results. We're going to launch our feature survey and we need a way to collect the results and receive email results. I'm thus proposing to use this committers list to collect the results (a mail is sent when someone fills in the poll). Note that we cannot publish results openly since: * there's an optional email address we can't put that in public * people may not want to share their results with everyone publicly Here's my +1 to the creation of this private committers list and for using it to send poll results. Thanks -Vincent

8 9

[xwiki-devs] [VOTE] Move JIRA macro to platform and make it a java macro
by Vincent Massol 26 Jan '12

26 Jan '12

Hi devs, I'd like to propose that we rewrite the JIRAwiki macro currently located at https://github.com/xwiki-contrib/macro-jira as a java macro in platform. Rationale: * Easier to debug and provide unit tests for * It's an important macro for our users * It's useful to us devs too since we use it on xwiki.org Here's my +1 Thanks -Vincent

7 6

[xwiki-devs] Call for test Extension Manager
by Thomas Mortagne 25 Jan '12

25 Jan '12

Hi xwikiers, I just add clustering support which was the last big peace of framework that was blocking a first fully functional version of Extension Manager. I will now dedicate my time to write tests and fix bugs and small improvements I find and try to fix some UI bugs too if Sergiu does not have time. I also have some improvement work in XWiki Repository and finally make extension.xwiki.org fully based on standard XWiki Repository and not have custom version anymore. During the 3.5 and 4.0 timeframe it would be nice to get as much tests and reports as possible on what is not working or still blocker in term or usability so that we get a nice and strong first version we can advertise in 4.0. There is obviously lots of possible improvements some of which you can find on http://dev.xwiki.org/xwiki/bin/view/Design/ExtensionManager (and I need to add more things in there) but I would like to limit to a fully working minimum for 4.0 and then do a priority survey on the many new features and improvements ideas. Here are the grey areas I know about and on which I'm going to concentrate on writing tests: * automatic xar merging is a quick implementation not excessively tested. Also the string properties content merging is not able to merge modification done on the same line which is not nice when things like the title is customized in the wiki and also changed in the new version of the xar. Right now in doubt the merge always take the new version when there is a conflict so that nothing is lost since it's easy to get back the previous version from the history. Also I'm not going to have time to work on a real manual conflict resolution UI for this timeframe, not alone at least. * clustering is a bit young ;) Also it expect all members to have the exact same constraints, if for any reason an extension is installed to a member and fail on another it could create quite a mess if that's an important extension. * it's not very hard to add versions and dependencies in XWiki Repository but it require using object editor which is not very nice for all profiles of users (now it's generally done by the developer of the extension so not a basic user either). Will try to work on that if I have some time left. Thanks, -- Thomas Mortagne

1 1

[xwiki-devs] [Proposal] New Feature survey for the 4.x cycle and beyond
by Vincent Massol 25 Jan '12

25 Jan '12

Hi devs, In 2009 we launched a survey on xwiki.org: http://www.xwiki.org/xwiki/bin/view/Main/SurveyXWikiFeatures2009 The results were published here: - http://www.xwiki.org/xwiki/bin/view/Blog/Features+Survey+Results - http://www.xwiki.org/xwiki/bin/view/Blog/FeatureStatus20120119 The idea is to do that same with a new survey. Benjamin Lanciaux (from XWiki SAS) has prepared one here: http://www.xwiki.org/xwiki/bin/view/Main/SurveyXWikiFeatures2012 Please let me know if you're ok and I'll send the survey on the user list. Thanks -Vincent

6 12

[xwiki-devs] XWiki Enterprise and XWiki Enterprise Manager 3.4 Released
by Marius Dumitru Florea 24 Jan '12

24 Jan '12

The XWiki development team is proud to announce the availability of XWiki Commons, XWiki Rendering, XWiki Platform, XWiki Enterprise and XWiki Enterprise Manager 3.4. XWiki Enterprise 3.4 is a stabilization release as we're approaching the end of the 3.x cycle so its main goal was to improve the Extension Manager and App Within Minutes features. However, this release also comes with a new look and a new default wiki page syntax. The highlights of this release are: * New color themes * XWiki 2.1 is the default page syntax * Improved Extension Manager UI * Delete space menu * Simple space templates * Special characters in attachment file names * Minimized action menu * Display macro See the full release notes at http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWikiEnterpris… for more details. Thanks -The XWiki dev team

1 0