June 2008 - xwiki-devs@xwiki.org

[xwiki-devs] DocHour day II !
by Thomas Mortagne 19 Jun '08

19 Jun '08

Hi community ! The second XWiki DocHour is planned on Thursday 19th of June. So what is this DocHour thing ? Here is the rules: * 1 hour * You choose at what time you want to work on the documentation. * On xwiki.org * You choose to document what you want. Ideas of missing documentation: - In JIRA: http://tinyurl.com/3xtn8t - Improve existing documentation - XWiki Watch documentation on http://watch.xwiki.org - XEM Documentation on http://manager.xwiki.org - XWiki Workspaces Documentation http://workspaces.xwiki.org * Make sure you create a jira issue for the work you're doing and assign to yourself. The issue should be created in the XWiki Core project, with a "documentation" component. Don't forget to tag it as "dochour20080619" to be listed in the result of this event. * If you can't do it on the the planned date, then you can still do it on another day, as close as possible to the the 19th of June ;) * The idea is to repeat this event every month or every 2 months. You can look at the result of previous DocHour at http://markmail.org/message/dm3kclit4g4s472v Thanks everyones and hope we will soon have to allocate more space to xwiki.org database ;) -- Thomas Mortagne

1 1

Re: [xwiki-devs] [xwiki-notifications] r10412 - in xwiki-platform/core/branches/xwiki-core-1.4/xwiki-core/src/main/java/com/xpn/xwiki: export/html pdf/impl plugin/charts plugin/graphviz plugin/image plugin/svg
by Vincent Massol 18 Jun '08

18 Jun '08

On Jun 18, 2008, at 6:32 PM, tmortagne (SVN) wrote: > Author: tmortagne > Date: 2008-06-18 18:32:27 +0200 (Wed, 18 Jun 2008) > New Revision: 10412 > > Modified: > xwiki-platform/core/branches/xwiki-core-1.4/xwiki-core/src/main/ > java/com/xpn/xwiki/export/html/HtmlPackager.java > xwiki-platform/core/branches/xwiki-core-1.4/xwiki-core/src/main/ > java/com/xpn/xwiki/pdf/impl/PdfExportImpl.java > xwiki-platform/core/branches/xwiki-core-1.4/xwiki-core/src/main/ > java/com/xpn/xwiki/plugin/charts/ChartingPlugin.java > xwiki-platform/core/branches/xwiki-core-1.4/xwiki-core/src/main/ > java/com/xpn/xwiki/plugin/graphviz/GraphVizPlugin.java > xwiki-platform/core/branches/xwiki-core-1.4/xwiki-core/src/main/ > java/com/xpn/xwiki/plugin/image/ImagePlugin.java > xwiki-platform/core/branches/xwiki-core-1.4/xwiki-core/src/main/ > java/com/xpn/xwiki/plugin/svg/SVGPlugin.java > Log: > Revert XWIKI-2483 (Lots of code don't take care of "xwiki.temp.dir" > when a temporary directory is needed) Explanation: I've asked Thomas to revert since I think this could be dangerous for our stable 1.4 branch and it's not an important bug anyway so it's better not to take the risk. Thanks -Vincent

1 0

[xwiki-devs] [VOTE] Release XWS 1.1 Milestone 2 tomorrow
by Jerome Velociter 18 Jun '08

18 Jun '08

Hello Devs, We have already slipped by one more week :( I underestimated the work needed for invitation management. Now we are about to be ready, thus I call a vote for releasing XWiki Workspaces 1.1 Milestone 2 tomorrow, with the following release notes : http://tinyurl.com/4dnbzf My +1 Regards, Jérôme.

5 5

[xwiki-devs] [Reminder] Bug Fix Day Number 2
by Vincent Massol 18 Jun '08

18 Jun '08

Hi everyone, This is our second bug fix day. Let the fun begin and let's try to break our previous record of last time (see http://tinyurl.com/6j6rvj for details) :) Here are the rules: * Every Wednesday all XWiki devs should work on fixing bugs only. * If they're not free on Wednesday they should do it on another day in the same week * The bugs should be taken in this order: a) bugs with patches available b) bugs planned for the current release. For example for 1.5M2 it's: http://tinyurl.com/5s2fjv c) bugs with the most votes: http://tinyurl.com/28yqvv d) bugs with higher severities Note that the URL i've given are for XWiki Core but the same applies for all JIRA projects and products. Right now we're planning to do this for Core, XE and XEM. I hope that this can be extended to other products such as Watch/Workspaces. Everyone is invited to help out and not just committers: * contributors can send patches * users can vote for their most important issues * bug reporters should be ready to verify that the fix does solve their problem Thanks -Vincent

2 1

Re: [xwiki-devs] [xwiki-notifications] r10391 - xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki
by Vincent Massol 18 Jun '08

18 Jun '08

On Jun 18, 2008, at 12:18 PM, tmortagne (SVN) wrote: > Author: tmortagne > Date: 2008-06-18 12:18:14 +0200 (Wed, 18 Jun 2008) > New Revision: 10391 > > Modified: > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > XWiki.java > Log: > Improve log > > Modified: xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/ > xwiki/XWiki.java > =================================================================== > --- xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > XWiki.java 2008-06-18 08:57:44 UTC (rev 10390) > +++ xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > XWiki.java 2008-06-18 10:18:14 UTC (rev 10391) > @@ -929,7 +929,9 @@ > } > > this.virtualWikiMap.set(host, wikiserver); > - } catch (XWikiException e2) { > + } catch (XWikiException e) { > + LOG.warn("Failed to find wiki name", e); would be great to say which wiki name was not able to be found. Thanks -Vincent

2 1

[xwiki-devs] [GSOC] Can't commit to sandbox
by malaka ekanayake 18 Jun '08

18 Jun '08

hi vincent/fabio I have completed the first version of the sample plugin for xwiki syntax colouring.But when i try to commit it to the sandbox I'm getting the following error First I checkout the plugin folder by svn co https://malaka@ svn.xwiki.org/svnroot/sandbox/plugins/ xwiki-sandbox-plugins then add my folder to the xwiki-sandbox-plugins folder and add it to the svn.when I try to commit my work by "svn co" it asked for the password .After entering the password it gives the following error svn: Commit failed (details follow): svn: MKACTIVITY of '/svnroot/sandbox/!svn/act/38ca4be0-0b6d-48c2-a151-04a2374fb9e3': 500 Internal Server Error (https://svn.xwiki.org) svn: Your commit message was left in a temporary file: svn: '/home/malaka/xwiki-repo/xwiki-sandbox-plugins/svn-commit.tmp' -- Malaka Ekanayake CSE UOM

3 2

Re: [xwiki-devs] [GSOC] Can't commit to sandbox
by Fabio Mancinelli 18 Jun '08

18 Jun '08

On 17 juin 08, at 21:13, Venkatesh Nandakumar wrote: > > Hi, > > Since my last mail to you and the list, this is what I've implemented. I am replying to the list. > > 1. Double Click Strategies :- double click selects appropriately > according to wiki syntaxes.... > 2. Advanced Indentation strategies, like for <dl> tags, enumerated > lists, new paragraph assist, etc. > 3. Word wrap functionality, goes in hand with new paragraph assist. > (minor) > 4. Code completion Assists, for egrecognises different enumerated > lists, > and automatically inserts it. > 5. Minor font change functionalities added to go in hand with syntax > highlighting > And the code, still has been implemented as a eclipse plugin.. Though > I'd soon be integrating it with xeclipse. If possible, could you set > me > up an account in the svn repository, and set up a separate branch > where > i would have commiting rights, so that I could upload my present work > and show them to you? > That's cool! Malaka who is working on this has also implemented an editor with initial syntax highlighting and he'll commit it soon. I cannot open accounts on the SVN repository so you must ask Vincent or someone else who has administrative rights for doing so. > Again Sir, What other functionalities are intended, like groovy/ > velocity > support, and where do I get information about its syntax etc? > Is there any other functionality that I have missed out? > Here we have to decide how to split the work because there is too much overlap. Starting from what Malaka and you have achieved until now I propose the following: 1) Malaka could concentrate on XWiki parser integration in the Eclipse text framework as previously discussed with Vincent here on the list. 2) You might discuss with Stephane to concentrate more on your project's objective that, if I am not wrong, are more semantic-web- related. 3) Both of you, since you are now expert on this field, could work together with us in order to integrate advanced feature, such as support for advanced sub-languages (this has also to be investigated with respect to how to well modularize the components). It is important, though, to have a code base where to start for, so the priority is to commit code in the sandbox so everybody will be in synch. WDYT? Cheers, Fabio

2 1

Re: [xwiki-devs] [xwiki-notifications] r10376 - xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki
by Vincent Massol 18 Jun '08

18 Jun '08

On Jun 17, 2008, at 6:55 PM, tmortagne (SVN) wrote: > Author: tmortagne > Date: 2008-06-17 18:55:46 +0200 (Tue, 17 Jun 2008) > New Revision: 10376 > > Modified: > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > XWiki.java > Log: > XWIKI-2477: Separate XWiki object creation from XWiki initialization > > Modified: xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/ > xwiki/XWiki.java > =================================================================== > --- xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > XWiki.java 2008-06-17 16:44:36 UTC (rev 10375) > +++ xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > XWiki.java 2008-06-17 16:55:46 UTC (rev 10376) > @@ -596,6 +596,11 @@ > return textarea.toString(); > } > > + public XWiki() > + { > + > + } > + this requires *lots* of comments... Thanks -Vincent

2 1

[xwiki-devs] [GSOC]anything new like jtidy
by Wang Ning 17 Jun '08

17 Jun '08

Hi, I have build a web app which can provide documents conversion service, both through web page or RESTful web service. All the documents are converted to html format. Now, I want to clean the result html. As discussed before, I go to JTidy[1]. Hense, I find that the last release of JTidy is published at August 1, 2001. I wonder if there is some more active project for html code cleaning, or JTidy is just sufficient? After clean the html, I will write some parser to convert html to xwiki syntax. All I have done is a web app which can run standalone. It accept input file, convert it to format file or purge xwiki syntax code, and output the result. I'm confused about how to develop it as a xwiki plugin. I know how to develop a xwiki plugin. As office import need upload file, output the result, I just don't know how to integrate it in to xwiki. Any suggestion will be very appreciated. Thanks. [1]http://jtidy.sourceforge.net/index.html -- Sincerely, Wang Ning

2 1

[xwiki-devs] Sorting JIRA issues
by Vincent Massol 17 Jun '08

17 Jun '08

Hi everyone, Just to let you know that I've taken the liberty of adding a new custom field in JIRA for Core called "Development Priority" with 3 values: low, medium and high. The idea is to categorize all our jira issues with this field in order to prioritize our efforts. Note that we're not using the existing Priority field since that field represents the priority from the user's point of view. Thus you're going to see lots of issue notifications coming in... sorry about that. If you don't agree about a given priority let us know as a comment in the issue. Note that the priorities are global, i.e. compared with other existing jira issues and not absolute. Thanks -Vincent

1 1

[xwiki-devs] SSO framework integration
by Markus Lanthaler 17 Jun '08

17 Jun '08

Hi, after evaluating possible frameworks I would propose to use OpenSSO [1] for my GSOC SSO project. It has full SAML 2.0 support, but lacks a bit regarding OpenID which isn't supported by default. There is an extension which allows OpenSSO to act as a OpenID 1.1 OP, but doesn't have RP support. OpenSSO has a very active and large community (which maybe is the strongest argument to use it). There are several requests for better OpenID support so I think that's a hot topic for them and maybe it's possible to find some other developers with whom I can add full OpenID 2.0 support. So now I'll start implementing RP support (authentication). As far as I understand the code I have to implement a XWikiAuthService analogous to the XWikiLDAPAuthServiceImpl, right? I also have some more questions :-) Let's start with OpenID (I'll start with that): 1.) I need to modify the login screen because I just need a field where the user can enter his OpenID URL, no password field. Then the user is redirect to his OpenID provider. How should/can I implement that? 2.) OpenIDs have to be bound to local user accounts (1:n relations, allow more OpenIDs per account) - how should this happen? In the admin GUI? Who should be allowed to do it? 3.) What about user registration? Should it be possible for users to create accounts without password and just OpenID? Please consider that XWiki should also be able to act as a provider, i.e. act as an OpenID server. Cheers, Markus -- [1] http://opensso.dev.java.net

5 7

[xwiki-devs] [VOTE] Overhaul of the administration, layout
by Jean-Vincent Drean 17 Jun '08

17 Jun '08

Hi XWikiers, Evelina has finished the ground work on the new administration and it's now time to vote for its layout. http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministration Proposals : Admin in view mode, with a left menu : http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministrationLayout1 Admin in view mode, without a left menu : http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministrationLayout2 Admin in edit mode, with a navigation panel : http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministrationLayout3 Admin in edit mode, without a navigation panel : http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministrationLayout4 Other question, how do we display the space selector : http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministrationSpaceSe… -- Jean-Vincent Drean

7 13

[xwiki-devs] [GSOC] Today is GSOC project starting day
by Vincent Massol 17 Jun '08

17 Jun '08

Hi GSOCers, The bonding period is over and today starts your GSOC project period. Note that this doesn't mean you should drop whatever JIRA issue you had assigned to yourself. Please continue to work on it and *finish* it. It's important. However it means that from today onwards you can start working on your project. The most important thing to do is send an email on the xwiki dev list explaining: * what architecture you're envisioning to use for your project. If you have doubts/questions please mention them. * A general planning breaking down the high level tasks you have to do and giving deadlines for each. That'll help you reach your objectives and in that manner we (the mentors and the community in general) can also help you by reviewing milestone objectives and helping you achieve them * what are your next steps and when you're planning to have them done * Any questions you have Please use the mailing list over IRC and especially over direct skype/ chat. Again it's really important that you work with the community. The success of your SOC depends on that as much as finishing your project. Thanks, good luck and have fun! -Vincent on behalf of the XWiki mentors

4 9

Re: [xwiki-devs] [GSOC] Can't commit to sandbox
by Fabio Mancinelli 17 Jun '08

17 Jun '08

On 17 juin 08, at 14:15, malaka ekanayake wrote: > Hi fabio > > I tried with both ways but getting the same error.Anyway I'll try > it again.In my previous mail I have attached my sample plugin.Can > you look at that one till I fix this issur and commit to the > sandbox.svn root will be fine.I'll commit to that path. Hi Malaka, I've looked at your code and you did a good job! It works pretty well though there are some things that must be improved (like the ones you were mentioning) Before I commit the code, could you please, do a bit of reformatting? Here at http://svn.xwiki.org/svnroot/xwiki/xwiki-platform/xwiki-tools/trunk/xwiki-v… you can find the .xml for the Eclipse formatter. This style is the style used by XWiki. I saw that that in your code there are some classes that probably are useless (is the TagRule used?) Could you please remove all the unused code inorder to avoid confusion? I also noticed that you incorporated verbatim some code from the tutorial (the tutorial's author name is in your code) Be careful when incorporating third party code. You must always check for licenses and compatibility and authorization!!! Ideally you should write all the code by yourself, even if when you use a framework you end up with writing more or less the same code. Could you check that the tutorial's code can be reused without restrictions? Please, keep the conversations on the XWiki devs list so that everybody can follow it. Send me a zip with the modifications and I'll commit it to the sandbox. After that, it's important to address Vincent's parser integration and spend some time on trying to figure out if and how it can be integrated in your work. I guess that Vincent's parser should be used as the partitioner, with it's output definining document's partition. But this has to be well investigated because it might be not so simple. Let me know. Cheers, Fabio

1 0

[xwiki-devs] [GSOC]Sample plugine
by malaka ekanayake 16 Jun '08

16 Jun '08

Hi fabio During the weekend I have written a sample plugine for xwiki highlighting some of xwiki syntax .Hear are the list of syntaxes which supports it. Titles ,Bulleted Lists,Text Styles,Info Macro<http://code.xwiki.org/xwiki/bin/view/Macros/InfoMacro> There are some improvements needed to be done . I am having some trouble with identifying composite syntax like bold & Italic. I think I will need your help on that. At the same time is there any reference to learn the jface API because at the moment only I have is the article you gave to me. I think I need to understand it more deeply .So any reference related to JFace Text API will be nice since :D. I will commit my work to the sandbox today. I didn't have time to look in to the Vincent's parser yet. I 'll start it by today.Meantime is there any news from Venkatesh cheers --Malaka Ekanayake CSE UOM

2 1

Re: [xwiki-devs] [xwiki-notifications] r10325 - xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF
by Vincent Massol 14 Jun '08

14 Jun '08

On Jun 14, 2008, at 3:10 AM, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2008-06-14 03:10:55 +0200 (Sat, 14 Jun 2008) > New Revision: 10325 > > Modified: > xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/web.xml > Log: > XWIKI-2117: encoding problems with AJAX adminstration utility > Fixed by not ignoring the specified character encoding sent by the > client. > > > Modified: xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/ > web.xml > =================================================================== > --- xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/ > web.xml 2008-06-14 00:31:23 UTC (rev 10324) > +++ xwiki-platform/web/trunk/standard/src/main/webapp/WEB-INF/ > web.xml 2008-06-14 01:10:55 UTC (rev 10325) > @@ -16,6 +16,10 @@ > <param-name>encoding</param-name> > <param-value>ISO-8859-1</param-value> > </init-param> > + <init-param> > + <param-name>ignore</param-name> > + <param-value>false</param-value> > + </init-param> Some comments on this init-param would be good I think, especially since the "ignore" name is pretty cryptic. Thanks -Vincent

1 0

[xwiki-devs] Mail Auth - done; 3 questions
by Lilianne E. Blaze 13 Jun '08

13 Jun '08

Hello, I just completed the modifications I mentioned in "Mail Problems" earlier. Seems to work just fine. XWiki.sendMessage redirecting to MailSenderPlugin, mail authorization ( = works with any smtp server, local or not), and means to provide additional Java Mail properties in Admin Prefs. I just need to test it a bit more and make patches and demo package. Should be ready in about 12-18 hours tops. Three things though: 1) I still have no idea what about the subject - it just defaults to "XWiki Message" in this version. 2) It needed mailsender plugin moved from plugins module to core module to avoid circulars and other nasties. 3) It still needs some sensible defaults and/or documenation for validation / confirmation content. Greetings, Lilianne E. Blaze

4 21

[xwiki-devs] ShortURLs?
by Lilianne E. Blaze 13 Jun '08

13 Jun '08

Hello, Is http://platform.xwiki.org/xwiki/bin/view/Main/ShortURLs final or a work in progress? Greetings, Lilianne E. Blaze

4 8

Re: [xwiki-devs] [xwiki-notifications] r10268 - xwiki-products/xwiki-enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/xpn/xwiki/it/selenium
by Vincent Massol 13 Jun '08

13 Jun '08

On Jun 12, 2008, at 1:50 AM, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2008-06-12 01:50:00 +0200 (Thu, 12 Jun 2008) > New Revision: 10268 > > Modified: > xwiki-products/xwiki-enterprise/trunk/distribution-test/selenium- > tests/src/test/it/com/xpn/xwiki/it/selenium/WikiEditorTest.java > Log: > XWIKI-1007: Removing all content in page has no effect & the content > of a wiki page is not allowed to be completely empty > Added integration test > > > Modified: xwiki-products/xwiki-enterprise/trunk/distribution-test/ > selenium-tests/src/test/it/com/xpn/xwiki/it/selenium/ > WikiEditorTest.java > =================================================================== > --- xwiki-products/xwiki-enterprise/trunk/distribution-test/selenium- > tests/src/test/it/com/xpn/xwiki/it/selenium/WikiEditorTest.java > 2008-06-11 23:49:28 UTC (rev 10267) > +++ xwiki-products/xwiki-enterprise/trunk/distribution-test/selenium- > tests/src/test/it/com/xpn/xwiki/it/selenium/WikiEditorTest.java > 2008-06-11 23:50:00 UTC (rev 10268) > @@ -158,4 +158,20 @@ > getFieldValue("content")); > // TODO: We need to find out how to make a text selection in > Selenium > } > + > + public void testEmptyContent() I'd suggest: testEmptyDocumentContentIsAllowed > > + { > + open("/xwiki/bin/edit/Test/EmptyWikiContent?editor=wiki"); > + setFieldValue("content", "this is some content"); > + clickEditSaveAndView(); > + assertFalse(getSelenium().isAlertPresent()); Why do we test for not having a dialog box present? There's content so why should that happen? If it's required the test should have some comments to explain it. > > + assertEquals(-1, getSelenium().getLocation().indexOf("/ > edit/")); I don't understand this either since we have clicked on save, we're no longer in edit and the url has view. Why verify this in this test which is about verifying that empty content is allowed. > > + assertTextPresent("this is some content"); Again why test this. The ability to enter content is already tested in other tests AFAIK. > > + open("/xwiki/bin/edit/Test/EmptyWikiContent?editor=wiki"); > + setFieldValue("content", ""); > + clickEditSaveAndView(); > + assertFalse(getSelenium().isAlertPresent()); > + assertEquals(-1, getSelenium().getLocation().indexOf("/ > edit/")); > + assertTextNotPresent("this is some content"); Is there a need to do the 3 tests which seem to be about the same verification? Thanks -Vincent

2 1

[xwiki-devs] retrieving XWIKI-generated page via javascript without headers
by rssh 13 Jun '08

13 Jun '08

Good day, community Yet one question: I want to retrieve xwiki page without header and footes via javascript, to save in dom-node. Now I search a principal way how to do this. I see two possible ways: A -- write special 'zero' skin // unfortunelly, I see that documentation on skins is outdated: in installation of svn version I see that velocity templates are situated outside skin. B -- try to use xwiki XML/RPC interface. (or may be add JSON-ORB as servlet) So, questions: - what approach (from this two) is prefferrable ? - where is documentation on xwiki XML/RPC interface ? Or some example of usage ? Are anybody tried to use XML/RPC interface from javascript. ? - may be still possible to reload (returning to first approach) view.vm template in skin. If yes - how ? P.S. (More detailed explanation what I want on code level: i. e. I want to write in xwiki page something like: <script> function update() { new Ajax.Reaqest('/xwiki.home/bin/view/My.Page', 'post' parameters { A: $('form.A').value, B: $('form.B').value, skin: 'zero' } onSuccess: function(transport) { $('result').innerHTML=transport.response; } ); } </script> <form> <input name='A' id='form.A' > <input name='B' id='form.B' > <button name='DO' onClick="update();" > </form> <div id="result">   </div> -- Ruslan Shevchenko GradSoft. http://www.gradsoft.ua

2 3

[xwiki-devs] Why /templates not in /WEB-INF?
by Lilianne E. Blaze 13 Jun '08

13 Jun '08

Hello, Is there any particular reason why /templates are not in /WEB-INF? I don't like the idea of having part of the source code accessible by everyone. Greetings, Lilianne E. Blaze

5 15

[xwiki-devs] Automatically migrating/adding wiki documents upon upgrade
by Jerome Velociter 13 Jun '08

13 Jun '08

Hello devs, I'm currently trying to find the best approach to automatically upgrade an XWS instance workspaces when upgrading the XWS version. By that, I mean adding new pages to existing workspaces for example. I see at least two possible approaches : * On display of the workspace, we check that the considered pages are present, and if not either we automatically create them, either we offer a big button to "upgrade" the workspace. (the test could be done in a skin template, so that any page would trigger the upgrade) * On plugin init, we search for all workspaces and upgrade the ones in need. And we could have a marker once the upgrade is done, not to execute the query at each init. WDYT ? Are there other approaches I'm missing ? Regards, Jerome.

3 5

[xwiki-devs] New WYSIWYG editor with or without dialogs?
by Marius Dumitru Florea 13 Jun '08

13 Jun '08

Hi devs, While working on the new GWT-based WYSIWYG editor, I find out that the default DialogBox from GWT moves very slow when dragged if it contains many HTML elements (like a table with 10 rows and 20 columns). In the current WYSIWYG editor dialog boxes are used for color picker, custom character, insert image / attachment / macro / table. Before I start porting these dialogs to GWT I'd like to ask you: Do you agree with using dialog boxes for these features? * if so, do you think it's ok to optimize the way they are moved by showing only their border while dragging (win95-like)? * if not, how can we replace them? Thanks, Marius

5 16

[xwiki-devs] [Rendering] XHTML parser
by Vincent Massol 13 Jun '08

13 Jun '08

Just to let you know (and especially Marius) that I've discovered that wikimodel has a XHTML parser already which seems to be doing quite a lot of things. I'll be trying it next week and integrate it into the new rendering module so that the new WYSIWYG module can use it. Thanks -Vincent

1 0

[xwiki-devs] It's voting time again: Help XWiki ! Vote for it's creator at a French radio contest !
by Ludovic Dubost 13 Jun '08

13 Jun '08

Hi XWiki users and developers ! It's voting time again.. You have helped me get through to the semi final a few month ago, and this week is the voting period for the semi-final. What's less fun is that this time we cannot not the current voting result in real time so we have to push as much as we can. You can vote here (in french too but that should not be too difficult ! Make sure you select the second person at the top !): http://www.radiobfm.com/bfm_academie/index.php This can give a nice additional boost to XWiki ! Thanks to all of you for you continuous support of XWiki and participation to the lists. Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

3 6

Re: [xwiki-devs] [xwiki-notifications] r10278 - xwiki-platform/web/trunk/standard/src/main/webapp/templates
by Vincent Massol 12 Jun '08

12 Jun '08

On Jun 12, 2008, at 5:08 PM, Sergiu Dumitriu wrote: > vmassol (SVN) wrote: >> Author: vmassol >> Date: 2008-06-12 10:08:57 +0200 (Thu, 12 Jun 2008) >> New Revision: 10278 >> >> Modified: >> xwiki-platform/web/trunk/standard/src/main/webapp/templates/ >> login.vm >> Log: >> XWIKI-2458: Ensure that the username field has the input focus in >> the login form so that it's easier for users to quickly log in >> Idea submitted by Mihail Agafonovs >> >> >> Modified: xwiki-platform/web/trunk/standard/src/main/webapp/ >> templates/login.vm >> =================================================================== >> --- xwiki-platform/web/trunk/standard/src/main/webapp/templates/ >> login.vm 2008-06-12 03:17:43 UTC (rev 10277) >> +++ xwiki-platform/web/trunk/standard/src/main/webapp/templates/ >> login.vm 2008-06-12 08:08:57 UTC (rev 10278) >> @@ -42,5 +42,11 @@ >> #xwikimessageboxend() >> </form> >> </div> >> +## Ensure that the username field of the login form has the focus >> to make it easy for users to log in quickly >> +<script type="text/javascript"> >> +//<![CDATA[ >> + document.forms.loginForm.j_username.focus(); >> +//]]> >> +</script> >> #template("endpage.vm") >> #end > > I don't like it. This is intrusive Javascript. I'd rather: > - add a class attribute, class="autofocus" > - write a global SkinExtension that focuses the first element with > that class, if it exists > - and execute that method onload, with Event.observe(window, "load", > autofocus) Actually before doing this I checked other vm files and I saw this was a common practice... So common but not good I guess :) I'm not sure why we would use a skin extension for a template. This is not about extending a skin, it's about common templates to all skins. I'd like to understand how the full current template structure is impacted by the new Skin Extension and what's the vision. Also AFAIK SkinExtensions are in wiki pages. I don't think it's a good idea to have pages for template stuff since template stuff work without a database. The solution you highlight also sounds very slow for performances. > What's missing now: global skin extensions don't work yet. We could, > for the moment, pull it in. WDYM by "pull it in"? Thanks -Vincent

1 0

[xwiki-devs] Bug Fixing Day Results for 11 June 2008
by Vincent Massol 12 Jun '08

12 Jun '08

Hi everyone, Yesterday was our first bug fixing day (which we intend to have every wednesday). The following bugs were fixed: http://tinyurl.com/5wcvs8 - Vincent * XWIKI-2454 XWiki products don't stop correctly under Tomcat - Sergiu * XWIKI-1007 Removing all content in page has no effect & the content of a wiki page is not allowed to be completely empty * XWIKI-1434 Case Related Issue With Backlinks * XWIKI-1045 halign and align {image} parameters overlap * XWIKI-2199 Saving a document via the inline editor resets the Tags document's property * XWIKI-1284 Image disappears from WYSIWYG editor in documents with special characters in name - Thomas * XWIKI-2453 Wrong use of cache in LDAP authenticator * XWIKI-2264 LDAP authentication does not support "." in login names - Artem * XWIKI-2375 Group and user access rights problem with a name which includes space characters So that's a total of 9 bugs fixed. Well done everybody and thanks to all who participated. Let's hope that even more of you can participate next wednesday. Thanks -Vincent

1 0

[xwiki-devs] the return of class/object management
by Pascal Voitot 12 Jun '08

12 Jun '08

Hello guys, do you remember my work on classes and objects? I fear the answer is "no" :) Anyway, I have been working on some other critical projects so I haven't been able to work on that for some time. But, now I have restarted my study for my current needs. The idea was to provide a simple way to manage classes, to delete/restore class properties and to synchronize objects with these classes. As I was not really happy about the result of my previous work based on class versioning (I found it too much intrusive in XWiki code and complicated), I totally changed my approach into something much lighter. The idea is really simple: I propose to add the feature of enabling/disabling class properties. * If you disable a property, it is only "hidden" without being deleted so you can modify the structure of the class without losing anything. * Then the disabled properties are also "hidden" for the objects instantiating this class and the valued fields are also not lost. * If you add a new property to the class, all objects will inherit a new field with the default value. * If you enable a disabled property, all the objects owning the field re-find it and the objects not having the field now have it with the default value. * you could also delete a disabled field from an object for some optimization issues. I also propose to add the "remove property" feature which would be quite protected but which is useful: you simply delete the property from the class. * All objects having the "removed" field are no more synchronized with the class. * the removed field still exist in the object but is no more available to classical display functions which use "class properties" to find object fields. * the removed field can be deleted from the object to resynchronize the object to the class * if a new property with the same type and name is re-added to the class, the object re-finds its existing field. The way to do it is quite simple: just add a "enabled" field to the PropertyClass and manage it in the code. I have modified a bit XWiki-Core and some velocity scripts but it seems really light without any really new logic Are you interested in this? best regards Pascal

3 3

Re: [xwiki-devs] [GSOC]syntax highlighting probleam
by Vincent Massol 12 Jun '08

12 Jun '08

Hi Venkatesh, On Jun 12, 2008, at 10:40 AM, Venkatesh Nandakumar wrote: [snip] > 1. Syntax Highlighting, to a large extent, though there have been > problems, as pointed out by Malaka, *bold~~combined~~bold* doesn't > give > the required effect, and secondly, the complex use of '*' in the wiki > syntax makes it a bit difficult to differentiate between actual *bold* > usage versus listing uses, maybe we would have to create own custom > regex-based rules for it later. For other tags, its been simple and > straightforward. Do you really need to parse it yourself? We have a parser in charge of doing this so you don't have to care at all about these problems. That's unless the system you use for syntax highlighting uses regexs (in which case I think it should be changed). Thanks -Vincent > > 2. Content Proposal, type <the first character of syntax> and drop- > down > of possible syntaxes, when selected, moves cursor to correct > position of > entry of text. Key-combination also brings down the menu. Also valid > for > applying styles to selected text. > 3. As a minor addition, context information. ( though very partially) > 4. Indentation strategies (very partial implementation till now) > 5. minor - Hyperlink detection and linking within {quote} and a > hyperlinks > > > I've also divided the document into partitions,(as of now, > pre,code,table,<dl> and default) for possibility of different content > proposal/content assist/syntax highlighting. > > I have not integrated any of the code with the xeclipse plugin's code. > What I have created as of now, is just another eclipse-plug-in. > > > Venkatesh > > > >

2 2

[xwiki-devs] Code commit
by Fabio Mancinelli 12 Jun '08

12 Jun '08

Hi everybody. I have some code to commit for XWIKI-2432 and XWIKI-2428... There has been a previous vote for my committership but no official announcement of the results (unless I missed it). So I am just asking for the official ok before committing the code in trunk. Cheers, Fabio

2 1

[xwiki-devs] [VOTE] Fabio Mancinelli as core committer
by Vincent Massol 12 Jun '08

12 Jun '08

Hi, I'd like to propose Fabio as a core committer. Fabio has been mostly participating in the rewrite of the XMLRPC support and I think it's important that he has access to maintain and improve it. Fabio's patches are very good too. In addition I believe Fabio is professional enough to not commit things he's not sure about if he's modifying other parts of the core and ask for core review instead. Last, if this make Fabio contributes to other parts in the core, then that's great for the project! Here's my +1 Thanks -Vincent

7 7

[xwiki-devs] [GSOC]syntax highlighting probleam
by malaka ekanayake 12 Jun '08

12 Jun '08

Hi fabio Regarding the xwiki syntax I have some questions. Up to now its straightforward to implement the highlighting for syntaxes like *bold*. *bold* can be easily identified by a "MultiLineRule" as a single partition. But it is possible for someone to write a *bold~~bold &italics~~bold*.Right ?. So this can go on and on.How should I tackle this problem. I think *bold~~bold &italics~~bold* should generate 3 partitions because partitions are non overlapping. *bold ~~bold &italics~~ bold* Is this right ?. Should I look into this problem later and implement the sample plugin for simple syntaxes like *bild*,~~italics~~ or not ? . cheers -- Malaka Ekanayake

3 3

Re: [xwiki-devs] [xwiki-notifications] r10277 - in xwiki-platform/web/trunk/standard/src/main/webapp: templates wiki_editor/plugins
by Vincent Massol 12 Jun '08

12 Jun '08

On Jun 12, 2008, at 5:17 AM, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2008-06-12 05:17:43 +0200 (Thu, 12 Jun 2008) > New Revision: 10277 > > Modified: > xwiki-platform/web/trunk/standard/src/main/webapp/templates/ > editwysiwyg.vm > xwiki-platform/web/trunk/standard/src/main/webapp/wiki_editor/ > plugins/attachments.js > Log: > XWIKI-1284: Image disappears from WYSIWYG editor in documents with > special characters in name > Fixed. > [snip] > > Modified: xwiki-platform/web/trunk/standard/src/main/webapp/ > wiki_editor/plugins/attachments.js > =================================================================== > --- xwiki-platform/web/trunk/standard/src/main/webapp/wiki_editor/ > plugins/attachments.js 2008-06-12 01:39:44 UTC (rev 10276) > +++ xwiki-platform/web/trunk/standard/src/main/webapp/wiki_editor/ > plugins/attachments.js 2008-06-12 03:17:43 UTC (rev 10277) > @@ -44,7 +44,7 @@ > var contextPathImage = > tinyMCE.getParam("wiki_images_path").toString(); > href = contextPathImage.substring(0, > contextPathImage.indexOf("/",2)) + > "/bin/" + href.substring(href.indexOf("/",3) + 1); > - href = unescape(href); > +// href = unescape(href); Shouldn't this be removed? > > var imgname_reg = new RegExp(this.getImagePath() + "(.*)", > "i"); > var r = imgname_reg.exec(href); > if(r) { > @@ -82,7 +82,7 @@ > if (halign != "") { > str += "<div class=\"img" + halign + "\">" > } > - str += "<img id=\"" + result[1] + "\" class=\"" + > this.IMAGE_CLASS_NAME + "\" src=\"" + this.getImagePath() + > result[1] + "\" "; > + str += "<img id=\"" + result[1] + "\" class=\"" + > this.IMAGE_CLASS_NAME + "\" src=\"" + escape(this.getImagePath() + > result[1]) + "\" "; > if( result[5] && (width = this.trimString(result[5])) != "") { > str += "width=\"" + width + "\" "; > } Thanks -Vincent

1 0

Re: [xwiki-devs] [xwiki-notifications] r10272 - in xwiki-platform/core/trunk/xwiki-core/src/main: java/com/xpn/xwiki/store/hibernate resources
by Vincent Massol 12 Jun '08

12 Jun '08

On Jun 12, 2008, at 2:47 AM, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2008-06-12 02:47:34 +0200 (Thu, 12 Jun 2008) > New Revision: 10272 > > Added: > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > store/hibernate/DocumentWebPropertyAccessor.java > Modified: > xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.derby.hbm.xml > xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.hbm.xml > xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.oracle.hbm.xml > Log: > XWIKI-2456: Deprecate the doc.web mapping and add doc.space in the > Hibernate mapping file > Done. > > > Added: xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/ > xwiki/store/hibernate/DocumentWebPropertyAccessor.java > =================================================================== > --- xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > store/hibernate/ > DocumentWebPropertyAccessor.java (rev 0) > +++ xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > store/hibernate/DocumentWebPropertyAccessor.java 2008-06-12 00:47:34 > UTC (rev 10272) > @@ -0,0 +1,69 @@ > +/* > + * See the NOTICE file distributed with this work for additional > + * information regarding copyright ownership. > + * > + * This is free software; you can redistribute it and/or modify it > + * under the terms of the GNU Lesser General Public License as > + * published by the Free Software Foundation; either version 2.1 of > + * the License, or (at your option) any later version. > + * > + * This software is distributed in the hope that it will be useful, > + * but WITHOUT ANY WARRANTY; without even the implied warranty of > + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU > + * Lesser General Public License for more details. > + * > + * You should have received a copy of the GNU Lesser General Public > + * License along with this software; if not, write to the Free > + * Software Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA > + * 02110-1301 USA, or see the FSF site: http://www.fsf.org. > + */ > +package com.xpn.xwiki.store.hibernate; > + > +import org.apache.commons.logging.Log; > +import org.apache.commons.logging.LogFactory; > +import org.hibernate.PropertyNotFoundException; > +import org.hibernate.property.BasicPropertyAccessor; > +import org.hibernate.property.Getter; > +import org.hibernate.property.PropertyAccessor; > +import org.hibernate.property.Setter; > + > +import com.xpn.xwiki.web.XWikiAction; > + > +/** > + * Hibernate property accessor that allows using the deprecated > <code>doc.web</code> in HQL queries, while using the > + * new <code>space</code> getter and setter for the actual object > access. > + * > + * @version $Id$ > + */ > +public class DocumentWebPropertyAccessor extends > BasicPropertyAccessor implements PropertyAccessor > +{ > + /** Logging helper object. */ > + private static final Log LOG = > LogFactory.getLog(XWikiAction.class); > + > + /** > + * {@inheritDoc} > + * > + * @see PropertyAccessor#getGetter(Class, String) > + */ > + @SuppressWarnings("unchecked") > + @Override > + public Getter getGetter(Class theClass, String propertyName) > throws PropertyNotFoundException > + { > + LOG.warn("Deprecated usage of doc.web property in HQL > query"); shouldn't we say: "Deprecated usage of doc.web property in HQL query, use doc.space instead." ? same below. Thanks -Vincent > > + return super.getGetter(theClass, "space"); > + } > + > + /** > + * {@inheritDoc} > + * > + * @see PropertyAccessor#getSetter(Class, String) > + */ > + @SuppressWarnings("unchecked") > + @Override > + public Setter getSetter(Class theClass, String propertyName) > throws PropertyNotFoundException > + { > + LOG.warn("Deprecated usage of doc.web property in HQL > query"); > + return super.getSetter(theClass, "space"); > + } > + > +} > > > Property changes on: xwiki-platform/core/trunk/xwiki-core/src/main/ > java/com/xpn/xwiki/store/hibernate/DocumentWebPropertyAccessor.java > ___________________________________________________________________ > Name: svn:keywords > + Id > > Modified: xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.derby.hbm.xml > =================================================================== > --- xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.derby.hbm.xml 2008-06-12 00:45:31 UTC (rev 10271) > +++ xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.derby.hbm.xml 2008-06-12 00:47:34 UTC (rev 10272) > @@ -66,10 +66,15 @@ > <column name="XWD_CREATOR" length="255" not-null="true" /> > </property> > > - <property name="web" type="string"> > +  > + <property name="web" type="string" update="false" > insert="false" > access="com.xpn.xwiki.store.hibernate.DocumentWebPropertyAccessor"> > <column name="XWD_WEB" length="255" not-null="true"/> > </property> > > + <property name="space" type="string"> > + <column name="XWD_WEB" length="255" not-null="true"/> > + </property> > + > <property name="content" type="string"> > <column name="XWD_CONTENT" sql-type="CLOB" > length="200000" not-null="true"/> > </property> > > Modified: xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.hbm.xml > =================================================================== > --- xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.hbm.xml 2008-06-12 00:45:31 UTC (rev 10271) > +++ xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.hbm.xml 2008-06-12 00:47:34 UTC (rev 10272) > @@ -58,10 +58,15 @@ > <column name="XWD_CREATOR" length="255" not-null="true" /> > </property> > > - <property name="web" type="string"> > +  > + <property name="web" type="string" update="false" > insert="false" > access="com.xpn.xwiki.store.hibernate.DocumentWebPropertyAccessor"> > <column name="XWD_WEB" length="255" not-null="true"/> > </property> > > + <property name="space" type="string"> > + <column name="XWD_WEB" length="255" not-null="true"/> > + </property> > + > <property name="content" type="string"> > <column name="XWD_CONTENT" length="200000" not- > null="true"/> > </property> > > Modified: xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.oracle.hbm.xml > =================================================================== > --- xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.oracle.hbm.xml 2008-06-12 00:45:31 UTC (rev 10271) > +++ xwiki-platform/core/trunk/xwiki-core/src/main/resources/ > xwiki.oracle.hbm.xml 2008-06-12 00:47:34 UTC (rev 10272) > @@ -60,10 +60,15 @@ > <column name="XWD_CREATOR" length="255"/> > </property> > > - <property name="web" type="string"> > +  > + <property name="web" type="string" update="false" > insert="false" > access="com.xpn.xwiki.store.hibernate.DocumentWebPropertyAccessor"> > <column name="XWD_WEB" length="255" not-null="true"/> > </property> > > + <property name="space" type="string"> > + <column name="XWD_WEB" length="255" not-null="true"/> > + </property> > + > <property name="content" type="string"> > <column name="XWD_CONTENT" length="200000" not- > null="true" sql-type="clob"/> > </property> > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications

1 0

Re: [xwiki-devs] [xwiki-notifications] r10270 - xwiki-products/xwiki-enterprise/trunk/distribution-test/selenium-tests/src/test/it/com/xpn/xwiki/it/selenium
by Vincent Massol 12 Jun '08

12 Jun '08

On Jun 12, 2008, at 1:53 AM, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2008-06-12 01:53:06 +0200 (Thu, 12 Jun 2008) > New Revision: 10270 > > Modified: > xwiki-products/xwiki-enterprise/trunk/distribution-test/selenium- > tests/src/test/it/com/xpn/xwiki/it/selenium/WikiEditorTest.java > Log: > [misc] Added a comment > > > Modified: xwiki-products/xwiki-enterprise/trunk/distribution-test/ > selenium-tests/src/test/it/com/xpn/xwiki/it/selenium/ > WikiEditorTest.java > =================================================================== > --- xwiki-products/xwiki-enterprise/trunk/distribution-test/selenium- > tests/src/test/it/com/xpn/xwiki/it/selenium/WikiEditorTest.java > 2008-06-11 23:51:17 UTC (rev 10269) > +++ xwiki-products/xwiki-enterprise/trunk/distribution-test/selenium- > tests/src/test/it/com/xpn/xwiki/it/selenium/WikiEditorTest.java > 2008-06-11 23:53:06 UTC (rev 10270) > @@ -159,6 +159,9 @@ > // TODO: We need to find out how to make a text selection in > Selenium > } > > + /** > + * See XWIKI-1007 > + */ Personally I don't like referring to JIRA issues like this because: 1) the reader has to navigate to the issue to understand what it is 2) there's the risk that in the future we'll use a tool other than jira So I'd prefer you simply say: "Verify that a document's content can be empty" or if you prefer " Verify that a document's content can be empty (see XWIKI-2007).". My preference for the former. BTW naming the test: testEmptyDocumentContentIsAllowed would be even better :) Thanks -Vincent > public void testEmptyContent() > { > open("/xwiki/bin/edit/Test/EmptyWikiContent?editor=wiki"); > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications

1 0

[xwiki-devs] [Reminder] Wednesday Bug Fixing Day tomorrow...
by Vincent Massol 11 Jun '08

11 Jun '08

This is just a reminder. See http://tinyurl.com/5ngsok Thanks -Vincent

1 1

[xwiki-devs] SSO support - status update
by Markus Lanthaler 11 Jun '08

11 Jun '08

Hi guys, I'm currently evaluating possible frameworks to use for my Single Sign On project (SSO). ESOE [1] and OpenSSO [2] both very promising, but both have their pros and cons. I didn't have a detailed look at JOSSO [3] yet. ESOE is licensed under the Apache 2.0 license, supports Shibboleth and OpenID (don't know yet which versions) and has authentication support for LDAP, Active Directory, and many more (comming). It also has support for multi-factor authentication. The downside of ESOE is that there isn't yet any final version available. It also can't act as a OpenID identity provider (OP) and needs an Apache module or IIS filter to act as an SAML provider. OpenSSO on the other hand has full SAML 2.0 support, but lacks a bit regarding OpenID which isn't supported by default. There is an extension which allows OpenSSO to act as a OpenID 1.1 OP, but doesn't have RP support. OpenID is licensed under Sun's Common Development and Distribution License (CDDL). So the next thing I'll do is to dig into JOSSO [3]. Do you know any other framework which I should consider? Regards, Markus -- [1] http://esoeproject.org [2] http://opensso.dev.java.net [3] http://www.josso.org

2 2

[xwiki-devs] [GSOC] [WebDAV] Ground work done.
by Asiri Rathnayake 11 Jun '08

11 Jun '08

Hi All, I think i made a mistake in my last update with the words "test framework". Actually what i meant is the basic environment setup and ground work. specifically, i wanted following things, * A maven project using ludovic's existing code (few modifications were done + a patch to the xwiki-core). * A way to easily build and deploy xwiki-webdav servlet. Now it's simply `mvn jetty:run` (uses hsqldb and a preconfigured database). * A platform independent WebDAV client so that anyone can test xwiki-webdav. Found DAVExplorer. * An eclipse project setup (M2Eclipse) that would allow anyone (that's me) to jump in and develop. I have committed my work (which has everything mentioned above) into http://svn.xwiki.org/svnroot/sandbox/xwiki-webdav/ . I have put a README along with it so that anyone can get started quickly. Btw, ludovic's original code is still available at http://svn.xwiki.org/svnroot/sandbox/webdav/ , should it be left as it is ? Now i will start to enhance xwiki-webdav and to add advanced DAV functionalities along the way. Please feel free to make comments / suggestions, they are always welcome. Thanks. - Asiri

2 3

Re: [xwiki-devs] ntlm with xwiki [END]
by Colin Tay 11 Jun '08

11 Jun '08

Hello, I have managed to authenticate users with the Active directory through LDAP. However, all the users i login were shown the error message "You are not allowed to view this document or perform this action." when i am at http://localhost:8080/xwiki/bin/view/Main/WebHome. I pressume the users records are not in the Xwiki database. Where and how do i create these records when the user first logon onto xwiki? Regards, ----- Original Message ---- From: arnaud <adlz(a)netcourrier.com> To: devs(a)xwiki.org Sent: Thursday, 15 November 2007 2:01:06 Subject: Re: [xwiki-devs] ntlm with xwiki [END] hello FYI it works !! just had to use the createUserFromLdap from Ldap plugin class now user are recognized by xwiki and authenticated by ntlm! At last! ----Message d'origine---- >Date: Mon, 12 Nov 2007 22:20:27 +0100 (CET) >De: "Jerome Velociter" <jerome(a)xwiki.com> >A: "XWiki Developers" <devs(a)xwiki.org> >Sujet: Re: [xwiki-devs] ntlm with xwiki > >Hi Arnaud, > >As far as your problem, I can't really help you much as I've never >experimented custom auth. I don't know how LDAP binds the users to actual >XWiki users, but I suppose for this to work, you should at some point feed >XWikiUsers documents/objects with data from LDAP. (since LDAPAuthImpl is >only auth, maybe there is something else needed). >Maybe you can ask this on the users list, as it is both more of a user >issue, and you could get insights from those who actually use LDAP >auth/user management. > >Good luck with this, >Jérôme. > >> >> hi again >> >> very sorry to disturbing you once again >> >> i saw that i can get request from wikicontext >> so in my own auth class i can get my user >> no longer need a servlet to send user to the login form >> great everything is fine BUT >> >> first: i still have "you are not allowed to view this document ...." when >> the user log in >> >> >> second : i can't log out >> >> problem look like xwiki don't know my user >> (in my AuthImpl i did all that it's found in LDAPAuthImpl...) >> >> sorry again >> (BTW if it's not the right place to ask this kind of questions, tell me, >> no problem...) >> >> >> >> >> >> >> >> >> >> >> >> ----Message d'origine---- >>>Date: Sat, 10 Nov 2007 23:19:23 +0100 (CET) >>>De: "Jerome Velociter" <jerome(a)xwiki.com> >>>A: "XWiki Developers" <devs(a)xwiki.org> >>>Copie à: devs(a)xwiki.org >>>Sujet: Re: [xwiki-devs] ntlm with xwiki >>> >>>Hello, >>>> >>>> First of all Sorry for creating a new topic >>>> >>>> thanks for your anwser Jerome. >>>> >>>> but Actually i have seen this feature >>>> >>>> i added jcifs and it works well >>>> an other hand i have tested impletentetion for ldap its works too >>>> >>>> but i want a transparent authentication >>>> so now the problem is : >>>> >>>> i would like to not have form login >>>> i saw in code that we can define our login page with this property in >>>> xwiki.cfg : >>>> xwiki.authentication.loginpage (if null default is >>>> /bin/login/XWiki/XWikiLogin) >>>> >>>> i've changed this property but no changes when template call >>>> >>>> $xwiki.getURL("XWiki.XWikiLogin", "login", "xredirect=$logredir")) >>>> >>>> i still got the same url : bin/login/XWiki/XWikiLogin? >>> >>>Actually, it's the expected behavior : the call asks for the URL of the >>>XWiki.XWikiLogin document, under the login action and with a xredirect >>>query string parameter. If you changed your authentication login page to >>>XWiki.MyCustomLogin in the conf, the calls to login URL should ask for >>>that document IMO. Also, you may have to modidy a bit the skin if you >>> want >>>the users to be redirected to the proper login page any case. If you are >>>using albatross skin, you can look over global.vm and login.vm, there is >>>also the header.vm file in the webapp/templates folder that calls for the >>>login URL. >>> >>>Hope it's clear enough, as I'm not sure what you exactly want to do (In >>>particuliar, I don't understand why you wany to post username to >>>loginsubmit action, since you use third-party authentication). >>> >>>Tell us how it goes. >>> >>>Regards, >>>Jerome. >>> >>>> >>>> >>>> the purpose of that is log-in link goes to my servlet , then i do ntlm >>>> authentication (it already works), then i post user name to >>>> /xwiki/bin/loginsubmit/XWiki/XWikiLogin >>>> >>>> in the same time i do my own version of authentification (get user info >>>> (name mail,etc...) from another ldap without test of password cos >>>> already >>>> done with ntlm) >>>> >>>> >>>> So! how can i redirect log-in page ? thanks a lot >>>> >>>> ------------------------------------------------------------ >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> Hi, >>>> >>>> You can implement your own version of the >>>> com.xpn.xwiki.user.api.XWikiAuthService interface. >>>> >>>> There's already a LDAP impl existing (different from the XWiki default >>>> one), so you can look over that too as an example. >>>> >>>> Then, you must precise in the xwiki.cfg configuration file that you >>>> want >>>> to use your own class, with something like >>>> >>>> xwiki.authentication.authclass = >>>> com.mycompany.mypackage.MyXWikiAuthImpl >>>> >>>> Regards, >>>> Jerome. >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> _______________________________________________ >> 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 > _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs __________________________________ Yahoo! Movies - Search movie info and celeb profiles and photos. http://sg.movies.yahoo.com/

2 1

Re: [xwiki-devs] New Administration Status & Implementation
by Vincent Massol 11 Jun '08

11 Jun '08

On Jun 11, 2008, at 9:08 AM, Evelina Slatineanu wrote: > Hi devs, > > > > I've updated > http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministration > with > the status and current implementation of the new administration app. > Please > review it and provide comments and suggestions before I make the first > patch. The css stylesheet are in development, so are the selenium > tests. > There is also a small but I couldn't fix so far, althouth I have a > workaround in mind. Hi Evelina, Can we seem a demo? That would be the best for us to provide feedback. right now what you've updated is very technical and hard for anyone to comment on. Thanks -Vincent

1 0

[xwiki-devs] New Administration Status & Implementation
by Evelina Slatineanu 11 Jun '08

11 Jun '08

Hi devs, I've updated http://dev.xwiki.org/xwiki/bin/view/Design/ImproveWikiAdministration with the status and current implementation of the new administration app. Please review it and provide comments and suggestions before I make the first patch. The css stylesheet are in development, so are the selenium tests. There is also a small but I couldn't fix so far, althouth I have a workaround in mind. Thanks, Evelina

1 0

[xwiki-devs] Jira down...
by Joshua Marks 11 Jun '08

11 Jun '08

Seems to have happened about 30 minutes ago. Joshua Marks CTO Curriki: The Global Education and Learning Community jmarks(a)curriki.org www.curriki.org US 831-685-3511

2 1

[xwiki-devs] Mail problems
by Lilianne E. Blaze 10 Jun '08

10 Jun '08

Hello, I'm using version 1.5 m1. While trying to register an user I'm getting error 553 - my smtp requires authenticating even from 127.0.0.1. Don't ask :/ I have a pretty good idea how to modify MailSenderPlugin to authenticate, but here's a surprise - it's not used. At least not when sending welcome mails. com.xpn.xwiki.XWikiException: Error number 10006 in 10: Could not send mail to s erver 127.0.0.1 port 25 error code 553 (553 sorry, that domain isn't in my list of allowed rcpthosts / Ta domena nie znajduje sie na liscie obslugiwanych przez serwer, jest zablokowana lub nieprawidlowo skonfigurowano uwierzytelnianie SMTP (#5.5.3 - vuser) ) at com.xpn.xwiki.XWiki.sendMessage(XWiki.java:3258) at com.xpn.xwiki.XWiki.sendMessage(XWiki.java:3294) at com.xpn.xwiki.XWiki.sendValidationEmail(XWiki.java:3199) at com.xpn.xwiki.XWiki.sendValidationEmail(XWiki.java:3162) at com.xpn.xwiki.XWiki.createUser(XWiki.java:3114) at com.xpn.xwiki.web.RegisterAction.action(RegisterAction.java:41) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:216) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:116) at org.apache.struts.action.RequestProcessor.processActionPerform(Reques tProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.ja va:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:119 6) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) It seems XWiki.sendMessage is deprecated, true, but still in use. Are there any plans to actually connect MailSenderPlugin any time soon? Adding authing in MailSenderPlugin would be trivial. Hacking it into current version of XWiki.sendMessage, well, that'd be less trivial. Any suggestions on what to do? I need it more or less working in about two weeks. Greetings, Lilianne E. Blaze

2 3

[xwiki-devs] How to manage existing spaces on workspaces product
by Sachin Mittal 10 Jun '08

10 Jun '08

Hi, We are building custom application over xwiki portal. A custom application is nothing but a space having some pages, plugins and custom skin. Space can be packaged as an application using application manager app. So far all is working fine. When we started the work the enterprise product was the best choice for us. So we imported this xar on top of platform and later extended the toucan skin to work against the new space we created. With time xwiki team created another product called workspaces which has made it much easier and simpler to organize workspaces and add applications to it. So we imported this xar on top of enterprise product and also added the needed plugins and skins for workspaces product. Everything worked fine. Now we want to have every user add existing spaces to his list of spaces. So that clicking on that space can take him to access that application. (or since we can package space as an application, have this new application along with existing ones available for import in his workspace). 1. So first question is how can make users add existing spaces or new application to his list? 2. If we want to choose some existing space as organization space or personal space, is that possible, if yes how? 3. What would be better for integrating spaces with user workspaces. Add them as space itself or package it as an application and make it available to import? 4. Also I notice that users that are not Admin when the login the top links of My Dashboard, My Profile and My Spaces are not working correctly. Document does not exist message is shown accessing them. Any idea why would it be so. So far workspace product seems a good approach handling spaces and users under it. However if we can manage existing spaces inside workspace it would really be a cool alternate to the enterprise product. Thanks in advance for any insight to the above queries. Sachin Mittal ----- http://www.assembla.com/wiki/show/sachin_mittal about me: -- View this message in context: http://www.nabble.com/How-to-manage-existing-spaces-on-workspaces-product-t… Sent from the XWiki- Dev mailing list archive at Nabble.com.

1 0

[xwiki-devs] Cant Load Plugin xwiki 1.4
by marlon hendred 10 Jun '08

10 Jun '08

Hi, I developed a plugin using the source i checked out of the trunk. I have build the war several times (with maven) to test the plugin and all has worked fine. Eventually after i was satisfied with my plugin. I jared up the classfiles using: $] jar cf my-plugin-1.0.jar com/xpn/plugin/myplugin/MyPlugin/*.class then i downloaded xwiki 1.4 from the xwiki site, and dropped my jar into the xwiki/WEB-INF/lib dir. Then i added: com.xpn.plugin.myplugin.MyPlugin to the list of active plugins in xwiki.cfg But when i tail catalina.out i see it complaining about not being able to find my plugin. Am i doing something wrong? Can someone please help me asap as we would like to go to production with this plugin. Thanks in advance. -Marlon

2 2

[xwiki-devs] LDAP Authentication exception
by shivshan 10 Jun '08

10 Jun '08

Hi On XE 1.4/Linux/Tomcat, i get the following exception when i try to post to a blog. Authentication works alright but sometimes, it seems as though it works in the second attempt. I know this is very strange. Any pointers? Using IE7 on Windows. Thanks Shiva 10:41:46,996 [http://172.21.16.147/xwiki/bin/view/Main/DocumentDoesNotExist] [http-80-1] WARN LDAP.XWikiLDAPAuthServiceImpl - LDAP authentication failed. com.xpn.xwiki.XWikiException: Error number 3201 in 3: Exception while saving document XWiki.shiva_shankar Wrapped Exception: Error number 3212 in 3: Exception while saving property tags of object XWiki.shiva_shankar Wrapped Exception: Illegal attempt to associate a collection with two open sessions at com.xpn.xwiki.store.XWikiHibernateStore.saveXWikiDoc(XWikiHibernateStore.java:573) at com.xpn.xwiki.store.XWikiCacheStore.saveXWikiDoc(XWikiCacheStore.java:97) at com.xpn.xwiki.store.XWikiCacheStore.saveXWikiDoc(XWikiCacheStore.java:91) at com.xpn.xwiki.XWiki.saveDocument(XWiki.java:1130) at com.xpn.xwiki.XWiki.saveDocument(XWiki.java:1098) at com.xpn.xwiki.XWiki.saveDocument(XWiki.java:1092) at com.xpn.xwiki.user.impl.LDAP.XWikiLDAPAuthServiceImpl.updateUserFromLDAP(XWikiLDAPAuthServiceImpl.java:725) at com.xpn.xwiki.user.impl.LDAP.XWikiLDAPAuthServiceImpl.syncUser(XWikiLDAPAuthServiceImpl.java:417) at com.xpn.xwiki.user.impl.LDAP.XWikiLDAPAuthServiceImpl.ldapAuthenticate(XWikiLDAPAuthServiceImpl.java:297) at com.xpn.xwiki.user.impl.LDAP.XWikiLDAPAuthServiceImpl.authenticate(XWikiLDAPAuthServiceImpl.java:107) at com.xpn.xwiki.user.impl.xwiki.MyFormAuthenticator.authenticate(MyFormAuthenticator.java:195) at com.xpn.xwiki.user.impl.xwiki.MyFormAuthenticator.processLogin(MyFormAuthenticator.java:96) at com.xpn.xwiki.user.impl.xwiki.XWikiAuthServiceImpl.checkAuth(XWikiAuthServiceImpl.java:213) at com.xpn.xwiki.XWiki.checkAuth(XWiki.java:3411) at com.xpn.xwiki.user.impl.xwiki.XWikiRightServiceImpl.checkAccess(XWikiRightServiceImpl.java:167) at com.xpn.xwiki.XWiki.checkAccess(XWiki.java:3419) at com.xpn.xwiki.XWiki.prepareDocuments(XWiki.java:4381) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:179) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.java:654) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDispatcher.java:447) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatcher.java:379) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher.java:292) at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:424) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:343) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:144) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Thread.java:595) -- View this message in context: http://www.nabble.com/LDAP-Authentication-exception-tp17750754p17750754.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

2 4

[xwiki-devs] [ANN] XWiki Enterprise Manager 1.2 released
by Thomas Mortagne 10 Jun '08

10 Jun '08

The XWiki development team is pleased to announce the release of XWiki Enterprise Manager 1.2. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This is the first release based on stable XE 1.4 branch. It include all XE 1.4 and 1.4.1 modifications and add new wiki creation/management features and improvements. For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Blog/XWikiEnterpriseManager12Released Thanks -The XWiki dev team

1 0

[xwiki-devs] [ANN] XWiki Enterprise 1.4.1 released
by Thomas Mortagne 10 Jun '08

10 Jun '08

The XWiki development team is pleased to announce the release of XWiki Enterprise 1..4.1. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This is an important bugfixes release (including one regression introduced in 1.4) mainly around multiwiki mode and encoding: * Global groups are not taken into account in a virtual wiki * Feed plugin's startUpdateFeedsInSpace does not allow to update two or more wiki with same space name in virtual mode * Macro Mapping does not initialize properly macro definition in multi wiki mode * The inline edit loses the doc's parent and title attributes * Wysiwyg editor breaks accents in links * Curly Quote coming from a Copy Paste is transformed into ? after cache is reset For more information see the Release notes at: [Main.ReleaseNotesXWikiEnterprise141] Thanks -The XWiki dev team

2 1

[xwiki-devs] LDAP Sessions
by mserel＠purecodeconsulting.com 10 Jun '08

10 Jun '08

Whenever a user authenticated via ldap trys to save to a wiki that he added a link to none of his changes are saved and it asks him to log back in? Has anyone heard of this? -Matt Starting release now On Mon, Jun 2, 2008 at 4:49 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote: > On Mon, Jun 2, 2008 at 3:08 PM, Vincent Massol <vincent(a)massol.net> wrote: >> >> On Jun 2, 2008, at 2:55 PM, Thomas Mortagne wrote: >> >>> I would like to release XEM 1.2 (based on XE 1.4.1) right after XE >>> 1.4.1 release, WDYT ? >> >> +1 if you want (not a high priority though since this is only for >> convenience and users can install XEM on top of a XE 1.4.1 release >> themselves). > > Yes but there is bugfixes in this release (not only 1.4RC1->1.4.1) and > there was no XEM/WikiManager "sable" release since 1.1.1 > (15/Apr/08)... > >> >> Thanks >> -Vincent >> >>> On Mon, May 26, 2008 at 9:58 AM, Thomas Mortagne >>> <thomas.mortagne(a)xwiki.com> wrote: >>>> On Mon, May 26, 2008 at 9:38 AM, Vincent Massol >>>> <vincent(a)massol.net> wrote: >>>>> >>>>> On May 26, 2008, at 9:36 AM, Thomas Mortagne wrote: >>>>> >>>>>> and now ? ;) >>>>> >>>>> Sounds good. >>>>> >>>>> Maybe you'll want till we can verify that the problem we're >>>>> having on >>>>> xwiki.org is not caused by 1.4? >>>> >>>> I prefer to have a XEM synchronized with XE in versions: 1.4->1.2, >>>> 1.4.1->1.2.1, etc. to be easier to follow for users (and us) but >>>> maybe >>>> it's not really needed ;). As you said, XEM is pretty easy to install >>>> from XE but I guess it's safer for user to be sure to have the right >>>> XEM version for the right XE version under it.... >>>> >>>>> >>>>> -Vincent >>>>> >>>>>> On Fri, May 16, 2008 at 3:36 PM, Vincent Massol >>>>>> <vincent(a)massol.net> >>>>>> wrote: >>>>>>> I agree with JV. We should wait. Especially since I don't see any >>>>>>> hurry and especially since users can create a XEM using 1.4 if >>>>>>> they >>>>>>> want. It's only a convenience distribution. >>>>>>> >>>>>>> Thanks >>>>>>> -Vincent >>>>>>> >>>>>>> On May 16, 2008, at 2:01 PM, Jean-Vincent Drean wrote: >>>>>>> >>>>>>>> +1 >>>>>>>> >>>>>>>> I think it would be wise to wait the middel/end of the next week >>>>>>>> to do >>>>>>>> the release, just to be sure there won't be an urgent need for >>>>>>>> a XE >>>>>>>> 1.4.1 >>>>>>>> >>>>>>>> On Fri, May 16, 2008 at 11:49 AM, Thomas Mortagne >>>>>>>> <thomas.mortagne(a)xwiki.com> wrote: >>>>>>>>> Hi devs, >>>>>>>>> >>>>>>>>> As XE 1.4 final is now released I would like to follow with >>>>>>>>> XEM 1.2 >>>>>>>>> final. The main "pure" XEM new feature is the wiki name ajax >>>>>>>>> based >>>>>>>>> validation, it also fix some bugs. >>>>>>>>> >>>>>>>>> See http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM12 >>>>>>>>> for >>>>>>>>> details. >>>>>>>>> >>>>>>>>> Here is my +1 >> _______________________________________________ >> devs mailing list >> devs(a)xwiki.org >> http://lists.xwiki.org/mailman/listinfo/devs >> > > > > -- > Thomas Mortagne > -- Thomas Mortagne _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

1 0

[xwiki-devs] [Vote] Release XEM 1.2 final
by Thomas Mortagne 10 Jun '08

10 Jun '08

Hi devs, As XE 1.4 final is now released I would like to follow with XEM 1.2 final. The main "pure" XEM new feature is the wiki name ajax based validation, it also fix some bugs. See http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM12 for details. Here is my +1 -- Thomas Mortagne

3 9

[xwiki-devs] Create a new page referencing a template
by Glenn Everitt 10 Jun '08

10 Jun '08

I'm trying to create a new document (page) and have the page reference a template. For example: #set($mydoc = $xwiki.getDocument("$myblogpage")) #if($mydoc.isNew()) ##new page created #set($content = "#template('blogmacros.vm')") $mydoc.setContent("$content") $mydoc.save() #end The problem is that all of the velocity statements are processed when added the template is added to the to the page. I tried to prevent processing by wrapping #template(.... with {pre}{pre} but it had no effect. So I tried to copy the document which already referrs to the template but this fails without any error message and never hits my breakpoint in XWiki.copyDocument #if(!$xwiki.exists("$myblogpage")) #if($xwiki.copyDocument($testpage , $myblogpage)) ##successfully copied #else ##failed to copy #end #end It seems like this should be easy what am I missing? Thanks for any help. Glenn Everitt -- View this message in context: http://www.nabble.com/Create-a-new-page-referencing-a-template-tp17741202p1… Sent from the XWiki- Dev mailing list archive at Nabble.com.

2 2

[xwiki-devs] Packaging application using application manager plugin
by Sachin Mittal 09 Jun '08

09 Jun '08

Hi, I recently created an application in xwiki. This was set of some classes and its objects. All the classes and objects are created in a space called aeternam. This space also contains some other data (mainly the pages that got created while testing the application). Now I want to select only the needed pages inside this space ie the classes that were created and some configuration objects and package them into a xar file. So that same can be imported in some other instance of xwiki as an application under the space aeternam. I believe application manager plugin would be best way to do this. If there is any other way to do what I just described please let me know that too. So I created a new application called aeternam application. I want to now add the classes and objects pages under aeternam space to it. Is there anyway to do this. When I click the edit link next to the application in application listing page, it does open an edit page, where there is a placeholder to add pages or documents. However, one cannot choose the documents from any link, one has to type it. Now there are many classes and objects I would like to package and it would not be possible for me to remember each document's name. So is there any better way of doing this with or without application manager app. Thanks Sachin ----- http://www.assembla.com/wiki/show/sachin_mittal about me: -- View this message in context: http://www.nabble.com/Packaging-application-using-application-manager-plugi… Sent from the XWiki- Dev mailing list archive at Nabble.com.

3 6

[xwiki-devs] Exception while saving document XWiki.XWikiPreferences
by Charles Baudin 09 Jun '08

09 Jun '08

I'm using Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 with jboss_4.0.3. I installed : xwiki-workspaces-web-1.0.war<http://forge.objectweb.org/project/download.php?group_id=170&file_id=10480> http://localhost:8080/xwiki/ HTTP Status 500 - ------------------------------ *type* Exception report *message* *description* *The server encountered an internal error () that prevented it from fulfilling this request.* *exception* javax.servlet.ServletException: Error number 3 in 0: Could not initialize main XWiki context Wrapped Exception: Error number 3201 in 3: Exception while saving document XWiki.XWikiPreferences Wrapped Exception: could not insert: [com.xpn.xwiki.doc.XWikiDocument] org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:535) org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:433) org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) javax.servlet.http.HttpServlet.service(HttpServlet.java:697) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) *root cause* com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not initialize main XWiki context Wrapped Exception: Error number 3201 in 3: Exception while saving document XWiki.XWikiPreferences Wrapped Exception: could not insert: [com.xpn.xwiki.doc.XWikiDocument] com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:303) com.xpn.xwiki.XWiki.getXWiki(XWiki.java:491) com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:123) org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) javax.servlet.http.HttpServlet.service(HttpServlet.java:697) javax.servlet.http.HttpServlet.service(HttpServlet.java:810) com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117) org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) Log message : 16:54:12,838 ERROR [AbstractFlushingEventListener] Could not synchronize database state with session org.hibernate.exception.GenericJDBCException: could not insert: [com.xpn.xwiki.doc.XWikiDocument] at org.hibernate.exception.SQLStateConverter.handledNonSpecificException(SQLStateConverter.java:103) at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:91) at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:43) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2267) at org.hibernate.persister.entity.AbstractEntityPersister.insert(AbstractEntityPersister.java:2660) at org.hibernate.action.EntityInsertAction.execute(EntityInsertAction.java:56) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:250) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:234) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:141) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:298) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1000) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:338) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at com.xpn.xwiki.store.XWikiHibernateBaseStore.endTransaction(XWikiHibernateBaseStore.java:783) at com.xpn.xwiki.store.XWikiHibernateBaseStore.endTransaction(XWikiHibernateBaseStore.java:754) at com.xpn.xwiki.store.XWikiHibernateStore.saveXWikiDoc(XWikiHibernateStore.java:447) at com.xpn.xwiki.store.XWikiCacheStore.saveXWikiDoc(XWikiCacheStore.java:97) at com.xpn.xwiki.store.XWikiCacheStore.saveXWikiDoc(XWikiCacheStore.java:91) at com.xpn.xwiki.XWiki.saveDocument(XWiki.java:1083) at com.xpn.xwiki.XWiki.saveDocument(XWiki.java:1056) at com.xpn.xwiki.XWiki.saveDocument(XWiki.java:1050) at com.xpn.xwiki.plugin.applicationmanager.core.doc.objects.classes.AbstractXClassManager.checkClassDocument(AbstractXClassManager.java:402) at com.xpn.xwiki.plugin.applicationmanager.core.doc.objects.classes.AbstractXClassManager.check(AbstractXClassManager.java:368) at com.xpn.xwiki.plugin.applicationmanager.doc.XWikiApplicationClass.getInstance(XWikiApplicationClass.java:260) at com.xpn.xwiki.plugin.applicationmanager.ApplicationManager.getApplicationList(ApplicationManager.java:184) at com.xpn.xwiki.plugin.applicationmanager.ApplicationManager.updateAllApplicationTranslation(ApplicationManager.java:378) at com.xpn.xwiki.plugin.applicationmanager.ApplicationManagerPlugin.init(ApplicationManagerPlugin.java:92) at com.xpn.xwiki.plugin.XWikiPluginManager.initPlugin(XWikiPluginManager.java:146) at com.xpn.xwiki.plugin.XWikiPluginManager.addPlugin(XWikiPluginManager.java:76) at com.xpn.xwiki.plugin.XWikiPluginManager.addPlugins(XWikiPluginManager.java:107) at com.xpn.xwiki.XWiki.preparePlugins(XWiki.java:858) at com.xpn.xwiki.XWiki.initXWiki(XWiki.java:786) at com.xpn.xwiki.XWiki.<init>(XWiki.java:722) at com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:293) at com.xpn.xwiki.XWiki.getXWiki(XWiki.java:491) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:123) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:697) at javax.servlet.http.HttpServlet.service(HttpServlet.java:810) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39) at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159) at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112) at java.lang.Thread.run(Thread.java:595)

1 0

[xwiki-devs] Any other comments to XWIKI-2428 (renamePage method)?
by Fabio Mancinelli 09 Jun '08

09 Jun '08

Dear all, I would like to add this improvement http://jira.xwiki.org/jira/browse/XWIKI-2428 I replied to Vincent's comment but there are no follow-ups. WDYT? Cheers, Fabio

2 3

[xwiki-devs] Active Directory: Log on permission to the DC is needed to authenticate
by mserel＠purecodeconsulting.com 09 Jun '08

09 Jun '08

All, I'm working on setting up active directory authentication for a xwiki site but our domain permissions only allow users to log onto certain computers for security reasons. The users do have permission to log onto the server that is hosting XWiki but when they try and authenticate they receive the LDAP data 531 error which means they do not have permission to log onto the workstation. When I add permissions to log onto the domain controller the users are then able to authenticate. Is there any reason that they need local login access to the DC/Is there any way to fix this? Thanks for your help! Sincerely, Matthew Serel

1 0

[xwiki-devs] [Proposal] Bug Fixing Day - every Wednesday
by Vincent Massol 08 Jun '08

08 Jun '08

Hi devs, Looking at jira we have 232 open bugs on core right now. This is quite worse than the figure we had when we release 1.4 final. In addition the diagram on jira.xwiki.org shows that more bugs are created than fixed lately. Since stability is one priority number 1 from now on (it's in the 1.5 roadmap as item 1) we need to do something about it. I think the main issue right now is that most of us are not working on bug fixing: * I am working on the new rendering module, required for the new WYSIWYG editor. * Jean-Vincent is working on the Administration overhaul w/ Evelina * ThomasM is working on the new cache implementation * Sergiu is working also on IX/Patch service * Artem is working on the JCR implementation We've discussed this with Thomas, Jean-Vincent and Sergiu this morning and the solution we've found is to initiate a "Bug Fixing Day". It would work as follows: * Every Wednesday all XWiki devs should work on fixing bugs only. * If they're not free on Wednesday they should do it on another day in the same week * The bugs should be taken in this order: a) bugs with patches available b) bugs planned for the current release. For example for 1.5M2 it's: http://tinyurl.com/5s2fjv c) bugs with the most votes: http://tinyurl.com/28yqvv d) bugs with higher severities Note that the URL i've given are for XWiki Core but the same applies for all JIRA projects and products. Right now we're planning to do this for Core, XE and XEM. I hope that this can be extended to other products such as Watch/Workspaces. We shall start this next Wednesday. Everyone is invited to help out and not just committers: * contributors can send patches * users can vote for their most important issues * bug reporters should be ready to verify that the fix does solve their problem Hope this is fine for everyone :) I've already collected +1 from Sergiu, Thomas, Jean-Vincent and myself. Thanks -Vincent

2 1

Re: [xwiki-devs] [xwiki-notifications] r10143 - xwiki-platform/core/trunk/xwiki-observation/src/main/java/org/xwiki/observation/event
by Vincent Massol 07 Jun '08

07 Jun '08

a unit test for this would be nice actually (I know I should have written it initially, sorry about that). -Vincent On Jun 7, 2008, at 5:09 AM, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2008-06-07 05:09:36 +0200 (Sat, 07 Jun 2008) > New Revision: 10143 > > Modified: > xwiki-platform/core/trunk/xwiki-observation/src/main/java/org/ > xwiki/observation/event/ActionExecutionEvent.java > Log: > XWIKI-2441: Comparing two ActionExecutionEvent always fails > Fixed > > > Modified: xwiki-platform/core/trunk/xwiki-observation/src/main/java/ > org/xwiki/observation/event/ActionExecutionEvent.java > =================================================================== > --- xwiki-platform/core/trunk/xwiki-observation/src/main/java/org/ > xwiki/observation/event/ActionExecutionEvent.java 2008-06-07 > 03:02:21 UTC (rev 10142) > +++ xwiki-platform/core/trunk/xwiki-observation/src/main/java/org/ > xwiki/observation/event/ActionExecutionEvent.java 2008-06-07 > 03:09:36 UTC (rev 10143) > @@ -71,6 +71,9 @@ > @Override > public boolean equals(Object object) > { > + if (object instanceof ActionExecutionEvent) { > + return getActionName().equals(((ActionExecutionEvent) > object).getActionName()); > + } > return getActionName().equals(object); > } > > @@ -82,7 +85,7 @@ > public boolean matches(Object otherEvent) > { > boolean isMatching = false; > - if > (ActionExecutionEvent.class.isAssignableFrom(otherEvent.getClass())) { > + if > (this.getClass().isAssignableFrom(otherEvent.getClass())) { > ActionExecutionEvent actionEvent = > (ActionExecutionEvent) otherEvent; > isMatching = > getActionName().equals(actionEvent.getActionName()); > }

1 2

[xwiki-devs] [GSOC]how to convert html to xwiki syntax
by Wang Ning 06 Jun '08

06 Jun '08

Hi, I have built a standalone plugin to convert MS Doc, MS excel to html. This plugin can run as a jar through command line or as a web application through url. Next, how to convert the html to xwiki syntax document? use xslt? Do the new rendering code have any influence? Now I can't handle the clipboard format. I think clipboard is at the second priority. My another question: how to add my code to xwiki code sandbox? Do I need to build ,test and distrubut my plugin by maven way? If yes, please tell how. Thanks very much. -- Sincerely, Wang Ning

9 21

[xwiki-devs] Xwiki XWS problem
by Jarmo Tanskanen 06 Jun '08

06 Jun '08

Hello, Thank you for the excellent workspaces application. I have tried it now and in the beginning all went OK but then came problem when listing All My Spaces. I got the error seen below. MySpaces page works fine with admin account but not with member account. version=1.1-milestone-1 groupId=com.xpn.xwiki.products artifactId=xwiki-workspaces-web environment: apache2, mysql5.0, tomcat5.5., debian linux (etch) How to fix this? Best Regards, Jarmo Tanskanen Error number 4001 in 4: Error while parsing velocity page XWS.MySpaces Wrapped Exception: Failed to evaluate content with id My Spaces <http://www.prepost-test.com:8180/xwiki/bin/view/XWS/MySpaces> com.xpn.xwiki.XWikiException: Error number 4001 in 4: Error while parsing velocity page XWS.MySpaces Wrapped Exception: Failed to evaluate content with id My Spaces <http://www.prepost-test.com:8180/xwiki/bin/view/XWS/MySpaces> at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:231) at com.xpn.xwiki.render.XWikiVelocityRenderer.render(XWikiVelocityRenderer.java:93) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:252) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:176) at com.xpn.xwiki.XWiki.include(XWiki.java:3511) at com.xpn.xwiki.api.XWiki.includeForm(XWiki.java:1372) at com.xpn.xwiki.api.XWiki.includeForm(XWiki.java:1338) at sun.reflect.GeneratedMethodAccessor237.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:294) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:194) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:145) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:117) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:226) at com.xpn.xwiki.render.XWikiVelocityRenderer.render(XWikiVelocityRenderer.java:93) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:252) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:176) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:145) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderDocument(DefaultXWikiRenderingEngine.java:134) at com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:423) at com.xpn.xwiki.api.Document.getRenderedContent(Document.java:371) at sun.reflect.GeneratedMethodAccessor240.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:294) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:145) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:117) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:226) at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1555) at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1476) at com.xpn.xwiki.api.XWiki.parseTemplate(XWiki.java:608) at sun.reflect.GeneratedMethodAccessor139.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:294) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:194) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:88) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:107) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:145) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:117) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:226) at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1503) at com.xpn.xwiki.web.Utils.parseTemplate(Utils.java:109) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:215) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Wrapped Exception: org.apache.velocity.exception.MethodInvocationException: Invocation of method 'contains' in class java.util.ArrayList threw exception java.lang.NullPointerException @ XWS.MySpaces49,100? <http://www.prepost-test.com:8180/xwiki/bin/edit/XWS/49%2C100?parent=XWS.MyS…> at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:286) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203) at org.apache.velocity.runtime.parser.node.ASTReference.evaluate(ASTReference.java:396) at org.apache.velocity.runtime.parser.node.ASTNotNode.evaluate(ASTNotNode.java:64) at org.apache.velocity.runtime.parser.node.ASTAndNode.evaluate(ASTAndNode.java:111) at org.apache.velocity.runtime.parser.node.ASTExpression.evaluate(ASTExpression.java:64) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:86) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74) at org.apache.velocity.runtime.directive.Foreach.render(Foreach.java:448) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:145) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:117) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:226) at com.xpn.xwiki.render.XWikiVelocityRenderer.render(XWikiVelocityRenderer.java:93) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:252) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:176) at com.xpn.xwiki.XWiki.include(XWiki.java:3511) at com.xpn.xwiki.api.XWiki.includeForm(XWiki.java:1372) at com.xpn.xwiki.api.XWiki.includeForm(XWiki.java:1338) at sun.reflect.GeneratedMethodAccessor237.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:294) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:194) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:145) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:117) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:226) at com.xpn.xwiki.render.XWikiVelocityRenderer.render(XWikiVelocityRenderer.java:93) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:252) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:176) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:145) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderDocument(DefaultXWikiRenderingEngine.java:134) at com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:423) at com.xpn.xwiki.api.Document.getRenderedContent(Document.java:371) at sun.reflect.GeneratedMethodAccessor240.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:294) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:145) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:117) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:226) at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1555) at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1476) at com.xpn.xwiki.api.XWiki.parseTemplate(XWiki.java:608) at sun.reflect.GeneratedMethodAccessor139.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:294) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:194) at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:170) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:88) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:107) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:145) at org.xwiki.velocity.DefaultVelocityEngine.evaluate(DefaultVelocityEngine.java:117) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:226) at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1503) at com.xpn.xwiki.web.Utils.parseTemplate(Utils.java:109) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:215) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.NullPointerException at com.xpn.xwiki.doc.XWikiDocument.equals(XWikiDocument.java:2073) at com.xpn.xwiki.api.Document.equals(Document.java:1439) at java.util.ArrayList.indexOf(ArrayList.java:220) at java.util.ArrayList.contains(ArrayList.java:201) at sun.reflect.GeneratedMethodAccessor286.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245) … 99 more

2 8

[xwiki-devs] [proposal] XWiki Watch 1.0 Roadmap
by ancapaula.luca＠xwiki.com 06 Jun '08

06 Jun '08

Here are proposed dates for the release of XWiki Watch: RC1 on 20 june RC2 / final on 27 june until when we plan to fix some remaining bugs, mainly focused on interface / skin issues and usage coherence. We'd also like to improve the scalability of watch (speed at high number of fetched articles), as long as this can be done without major architecture impact. You can find the complete list at http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10200&… . Here's my +1, What do you think?

2 2

[xwiki-devs] Logging architecture proposal
by Jonas von Malottki 06 Jun '08

06 Jun '08

Hello X-Wikians, I am currently browsing the Xwiki Code and thus found the current handling of the logging to catch my eye. I filed a jira idea (XWIKI-2437) to use slf4j as logging abstraction. it wasn't until this mornig though that I found the new logging Architecture in the component sub part, and also Vincent pointed me 20 minutes later to it. Still even with the logging pushed through the org.xwiki.component.logging.Logger interface I have a suggestion. A very good thing at the slf4j and particularly one of the implementations is that building of the logging strings can be deferred to the logger. I will explain that with an example: Current Logger interface you will have to do this (or something similar) LOG.debug("my debug message is " + var1 + " " + var2 + ": " + var3 ); This will force the Java VM to build the string and then call the function to realize later that the string will not be logged. Now one could introduce an if statement with log.isDebugEnabled() before any such statement, but that is kind of tedious and clutters the code. In slf4j you would write something like this: LOG.debug("my debug message is {} {}: {}", var1, var2, var3); Thus the function will be called but the string operation can take place iff the string will really be logged. (see http://www.slf4j.org/manual.html) So my proposal is to give the logging interface a little bit of slf4j flavor and introduce log statements with varargs or Object arrays like: public void debug(String msg, Object... args); /* plus all the other loglevels */ If one wants to use log4j then a simple wrapper could be written to format those args before log it depending on the loglevel. Thinking a bit further, slf4j does already that what it is intended with the new component logger since the implementations are deploytime pluggable (currently logback, simple logger, log4j and jcl can be used as backend) and slf4j is just a facade to the logging system, thus fulfilling the component based approach. Since reuse is better than reinvent... cheers Jonas

2 3

[xwiki-devs] SX questions
by Vincent Massol 06 Jun '08

06 Jun '08

Hi (Sergiu), I finally read your SX design doc yesterday night and I have some questions: * It's called Skin Extensions (SX) but it seems to be missing vm extensions, right? AFAIU this is in IX. I would have expected Skin extensions to include vm. Maybe just a problem of terminology. * How do you manage CSS/JS that depend on the skin used. For ex you took the example of usersandgroups.css in your doc but that CSS is different for Albatross and for Toucan. How do we handle this? * Now that it's implemented, would be nice to move the doc to the developer's guide and add some examples. Also do you know where in the code this is used right now? * Has there been some measurements to see how performance is affected? Thanks a lot, sounds very cool. -Vincent

2 1

[xwiki-devs] Setting TAGs in XWiki workspaces
by Vivian Richard 06 Jun '08

06 Jun '08

Hello Vincent, Pressing EDIT button on XWiki Enterprise wiki page shows the TAG list attached to a page aloowing them to be changed. I do not see it here in workspaces. How do I get that in XWiki workspaces so that I may set/reset TAG values. Best Regards, Viv

2 1

[xwiki-devs] New Rendering in core, what can you expect?
by Vincent Massol 05 Jun '08

05 Jun '08

Hi, Just committed the new rendering mechanism in xwiki core. Please note that this is a work in progress and it's missing a LOT of things. However we can now all work together on finishing it. Here's how it works: * Each document has a syntax id, which defaults to XWiki 1.0 * In edit mode (Toucan skin), you can change the syntax for a page using the Document Information panel on the right What's supposedly working in the new syntax: * basic wiki syntax, lists, paragraph. Not everything is done yet and there are some bugs in the WikiModel XWiki parser * velocity macro, xhtml macro and include macro Try it out and have fun, just don't expect too much yet... ;) -Vincent

2 3

Re: [xwiki-devs] Refactoring Administration and Preferences
by Evelina Slatineanu 05 Jun '08

05 Jun '08

Hi all, Besides working on the new Administration, I also did some clean up for the existing apps (blog, photos, calendar), making them platform applications. The question is: should I place the pages in app. specific spaces (ex. Blog, Calendar, Photos) and also update all the links to the new apps in all xwiki docs (I have already a 80% finished version of this kind) or should I leave the files in the XWiki space? (as Jv mentioned, we might need to keep the compatibility for older clients because most of the pages which need updates are classes, so this could break possible hand-made queries) Thanks, Evelina

1 0

[xwiki-devs] exception when saving wiki in editor(wiki)
by CarrollJ 05 Jun '08

05 Jun '08

Hi all, I have a problem when saving a wiki in the wiki editor. When it is saved an exception occurs (below). When i then view the page after the exception it works fine. Does anyone have any suggestions on what i can do to fix it? Thanks, John Carroll A problem occured while trying to service your request. Please contact the support if this happens again. Detailed information: Error number 3201 in 3: Exception while saving document StageGate.WebHome Wrapped Exception: Error number 13012 in 3: Exception while saving links Wrapped Exception: Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect): [com.xpn.xwiki.objects.LargeStringProperty#] -- View this message in context: http://www.nabble.com/exception-when-saving-wiki-in-editor%28wiki%29-tp1766… Sent from the XWiki- Dev mailing list archive at Nabble.com.

2 2

[xwiki-devs] [GSOC][WebDAV] Status ...
by Asiri Rathnayake 05 Jun '08

05 Jun '08

Hi All, I thought it's better to keep you all updated about what i'm doing. I've finally managed to free myself from academics and now i'm working on WebDAV interface. * I have gone through Ludovic's sample XWikiWebDAV implementation and except for few parts now i understand the code base and what i need to do. And i should mention that this sample implementation was very useful, i would have lost otherwise ;) * I've put up an eclipse project with WTP (Web Tools Platform) support which let me test the DAV implementation easily. Also, using M2Eclipse i have created a pom as well. * Currently, with a back-end xwiki database, i can test the DAV interface via nautilus (linux file explorer) embedded WebDAV client. Only browsing is functional at this point. * I would like to commit this test framework (currently it doesn't have any of my own code) into sandbox along with a README file so that anyone can test it. But i need instructions on how to do it. Please feel free to make comments and suggestions. I'm really sorry this mail took so long, i was bit busy. Thank you all. - Asiri

2 7

[xwiki-devs] XWikiLDAPAuthService
by Fabien 05 Jun '08

05 Jun '08

Hi again, During my search into LDAP code, I found that the xwiki.cfg check_level was removed in the new XWikiLDAPAuthService that deprecate the LDAPAuthService. It is a pity because for my pb I only need to check if the LDAP Bind is ok or not to authenticate my user, and this works perfectly (except the allocated XwikiGroup) with the old LDAP authentication mechanism. Is it possible to re-add the check_level param in the current XwikiLDAPAuthService ? Fabien

2 3

[xwiki-devs] Failing build...
by Vincent Massol 05 Jun '08

05 Jun '08

It took me a while sorry but I think I've fixed it (building now). The pb is that the new context module was not added in Continuum. I had a problem with my user account there (I was locked out), that's why it took me some time. Sorry. Thanks -Vincent

2 3

[xwiki-devs] aspect compilation problem under Eclipse with JAVA6.0 ???
by Pascal Voitot 05 Jun '08

05 Jun '08

Hello, I compiled the whole packages from trunk under Eclipse running with a JDK1.6_06. When I launch XWiki-Enterprise, it stops while instantiating Hibernate Storage with an error "can't find web property in XWikiDocument"... which is true because web is managed by get/setSpace... I discovered the get/setWeb is provided for compatibility by an aspect... So, I took a look at the compiled aspects and the generated .class were really smaller than the one in a JAR from the repository... After some unsucessful tries, in Eclipse, I decided to switch from java6.0 syntax to java5.0 and recompiled and then I got some .class which seemed bigger... Then I launch XWiki and it now works... Has anyone encountered the same problem? regards Pascal

2 1

[xwiki-devs] Releasing spacemanager 1.0.1
by Jerome Velociter 04 Jun '08

04 Jun '08

Hello devs, Just a short note to inform you I'm about to release spacemanager 1.0.1 version. This is a bug fix version that is mainly needed for the curriki project (spacemanager 1.0 branch rely on core 1.3). It has the following release notes : http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10301&… Regards, Jerome.

1 0

[xwiki-devs] Tip for writing new component depending on xwiki-core
by Vincent Massol 04 Jun '08

04 Jun '08

Hi, Just wanted to share this tip. Imagine that you need to write a new module but it requires some dependency on xwiki-core and xwiki-core also needs to use this new module... This is often the case since we haven't moved the model to a new module yet. So how do you solve this circular dependency? Solution: * In your new module, create a component interface to isolate the new code from xwiki-core * Use component to lookup the implementation. This will only be resolved at runtime. * Implement the component interface in xwiki-core Hope it'll help someone -Vincent

1 0

[xwiki-devs] [gsoc] syntax highlighting and code assistance
by malaka ekanayake 04 Jun '08

04 Jun '08

hi fabio, It will get another 2 days to get my new internet connection.So what should I do till I get my connection.Unfortunately I will not be able to look at the new XE release.:-( Should I look in to implement syntax assistance for one language (xwiki syntax) or should I need to think of all the syntax at the first since xwiki pages will include a mix of several syntaxes .The article I have found explains how to implement syntax for SQL.I think by getting help from you I will be able to implement syntax asistance for one laguage.So what path I should take. -- Malaka Ekanayake CSE UOM

2 1

[xwiki-devs] n umber of maximum BLOGS in xwiki
by Vivian Richard 04 Jun '08

04 Jun '08

Hello Devs, is there any limitations on how many BLOGS can be created on one installed XWiki. Some one told me that the maximum six person can create six different blogs in one XWiki. Is it true? Best regards Viv

4 10

Re: [xwiki-devs] Refactoring Administration and Preferences
by Jean-Vincent Drean 04 Jun '08

04 Jun '08

On Wed, Jun 4, 2008 at 11:05 AM, Evelina Slatineanu <evelina.slatineanu(a)xwiki.com> wrote: > Hi all, > > I have a question: should we also keep the old interface for users, groups > and rights in the new Administration application? (the current interface is > now set from xwiki.cfg but the default one is the new UI). Is there a point > to keep the old one (for older customers, no js browsers??) > AFAIK we've added this option because the new rights UI hasn't been tested enough at that time, I think we can consider it as stable enough to be the only rights editor now. OTOH it won't work with javascript disabled, but the object editor will .. I'm not sure about this one. XWikiers WDYT ? -- Jean-Vincent Drean

2 1

Re: [xwiki-devs] [xwiki-notifications] r177 - in components/xwiki-rendering: xwiki-rendering-api/src/main/java/org/xwiki/rendering/block xwiki-rendering-api/src/main/java/org/xwiki/rendering/macro xwiki-rendering-api/src/main/java/org/xwiki/rendering/parser xwiki-rendering-api/src/main/java/org/xwiki/rendering/transformation xwiki-rendering-api/src/test/java/org/xwiki/rendering xwiki-rendering-doxia xwiki-rendering-doxia/src/main/java/org/xwiki/rendering/doxia/internal xwiki-rendering-doxia/src/main/java/or
by Sergiu Dumitriu 04 Jun '08

04 Jun '08

vmassol (SVN) wrote: > Author: vmassol > Date: 2008-06-03 20:58:01 +0200 (Tue, 03 Jun 2008) > New Revision: 177 > > Log: > XWIKI-654: Rewrite the Rendering engine > > * Renamed Document into DOM. This is a better name and not in conflict with the XWiki Document. The other option was to name it DocumentAST or AST. Jean-Vincent preferred DOM and I agreed with him, although it was a close call ;) I'm not sure DOM is a good name, as it already stands for something else. -- Sergiu Dumitriu http://purl.org/net/sergiu/

2 3

[xwiki-devs] [VOTE] Move new rendering code to the platform core?
by Vincent Massol 04 Jun '08

04 Jun '08

Hi, I'm ready to move the new rendering code currently located in the sandbox to the platform core. I have succeeded in doing some basic integration in the core and I think it's time to commit this too. This is how it works: * I've introduced a new syntaxId database field for documents * When the syntaxId value is null/empty or has a value of "xwiki-1.0" the old rendering is used * When it has a value of "xwiki-2.0" the new rendering is used I'm working on providing a way (for admins only for now) so that in edit mode you can choose the syntax id to use for the page. Right now I'd just like us to vote to move the new rendering code to the platform core. Here's my +1 Thanks -Vincent

6 5

[xwiki-devs] Refactoring Administration and Preferences
by Sergiu Dumitriu 04 Jun '08

04 Jun '08

Hi devs, This is somewhat in response to the discussion about the new Administration page design. Behind the scenes, there was a discussion about where should the Import page put the uploaded xar, in XWiki.Import (as it is done now), or in XWiki.XWikiPreferences. Both sides agreed that the administration should automatically find and use administration pages, but didn't agree on what "use" means. So, how should things work? A. The main administration page contains links to other pages B. The main administration page includes other administration sheets Option A means that each administration topic uses its own page to store configuration, which somehow breaks the current configuration mechanism, where all (global) settings go into the XWiki.XWikiPreferences page. Option B means that each administration document is used only as a sheet, so all objects will be in XWiki.XWikiPreferences. If we choose B, then the best thing to do is to attach imported xars to the XWikiPreferences page, instead of Import. Doing otherwise will either be very hard or would break the convention. So, the main question is: Do we keep all settings in the same document? Or do we allow each application/component to have its configuration in its own document? I think it would be better to have all the configuration in one place, instead of spreading it all over the wiki. And since we're touching the configuration part, I think we should completely rewrite this part, as the current system is sooo bad (I mean the XWiki#get[User/Web/XWiki]Preference[AsSomething] methods and the giant XWikiPreferences class). This was supposed to be a Configuration proposal that I was thinking about, but didn't have the time to write until now. So here it is: Requirements: 1. We should allow an application/component to be configured at the farm, wiki, space, user and document level (the specificity can be configured for each setting), with static values in the component's xml configuration and default values in the java class file or in the template/wiki document using the configuration (depending on whether there is a component/java/template part). 2. An application should be able to define its own customization xclasses, the same class being usable for all levels of customization (now, some settings go both in XWikiUsers class and XWikiPreferences class). In fact, XWikiPreferences should disappear completely. 3. Global (farm) settings should go in [mainwiki]:Admin/GlobalPreferences, wiki settings should go in Admin/WikiPreferences, space settings should go in <Space>/SpacePreferences, user settings should go in the user profile. The current locations are inappropriate (WebPreferences??). [I'm not sure if Preferences is a good name, as the list of blog categories is not exactly "preferences", but more like "settings"] 4. The settings pages include an administration sheet, which later lists all customization pages in the wiki that are customizable at that level (for the moment, using an explicit search, later using Interface Extensions). 5. The configuration should be accessible using a simple API, which should find the right settings, internally taking care of all the details: consider the lowest level for that setting (some settings are valid only at the wiki level, or even global, so don't search or allow settings at a lower level), security (some settings should only be taken into consideration if the author is trusted), in-wiki and in-file settings. This means that the application should call one method, and not have a complicated code combining getUserPreference, getWebPreference, getXWikiPreference and Param. 6. All this should be done without changing the data model (meaning that we use the classic xclasses/xobjects for this). How things work: An application lists one or several wiki documents in its application description as customization classes. Administration sheets (also from the application) are then autoincluded in the global, wiki or space Administration page, and in the user settings page. Such a sheet would check if the class allows customization at the current level, and if not, warns about this. If there is no instance of the target class, it provides a link for creating one (doing it automatically is another option, but I don't think it is a good idea, as this pollutes the wiki with unused objects). The sheets should follow a common guideline, for consistency. All options should be documented in the sheet. The application code then calls the settings component API to check the settings that apply for the current document/user. Of course, all this with lots of caching for good performance (this is not the case in the current core, as a lot of time is spent cloning XWikiPreferences in HibernateCacheStore). The hard part is deciding how to configure these classes and sheets. Since we shouldn't use different Property types, we can't add a customizationLevel metaproperty. A feasible solution would be to require all properties in the same class to have the same level of configuration, and either specify in the application description, or use a tag for that. The best would be to have a document property, but the current data model does not have that. Proposed API variant 1: /* Gets the current setting for an application, from the specified class. */ String getSetting(applicationName, className, settingName); /* Same as above, when the application has only one settings class defined. */ String getSetting(applicationName, settingName); /* If the current document is known to belong to a certain application, get a setting for that application */ String getSetting(settingName); /* Stops at a specified level, instead of the default one. */ String getSettingForLevel(applicationName, className, settingName, maxLevel); /* Returns the setting at a specified level, with no inheritance. */ String getSettingAtLevel(applicationName, className, settingName, exactLevel); Proposed API variant 2: /* Search for the setting name in the attached objects. */ String getSetting(settingName); /* Gets the current setting, from the specified class. */ String getSetting(settingName, className); /* Stops at a specified level, instead of the default one. */ String getSettingForLevel(settingName, className, maxLevel); /* Returns the setting at a specified level, with no inheritance. */ String getSettingAtLevel(settingName, className, exactLevel); - I don't know if we need methods returning other types, like int or double, since we can use velocity tools for converting the returned string - I don't know if we should have the applicationName in the parameter list, or just the className; my take is that specifying the application name is a bit more semantical and less technical - maxLevel should be an enum, but we need a custom introspector for this to work - maxLevel assumes a fixed order of levels, which is an obvious one, except for the User level. Where should that be in this order? Is the user preference the most important one? So, WDYT? -- Sergiu Dumitriu http://purl.org/net/sergiu/

3 5

Re: [xwiki-devs] [xwiki-notifications] r10099 - xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/stats/impl
by Vincent Massol 04 Jun '08

04 Jun '08

On Jun 4, 2008, at 4:52 AM, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2008-06-04 04:52:41 +0200 (Wed, 04 Jun 2008) > New Revision: 10099 > > Modified: > xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > stats/impl/StatsUtil.java > Log: > [misc] Don't use a local variable to hide the class member. > > > Modified: xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/ > xwiki/stats/impl/StatsUtil.java > =================================================================== > --- xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > stats/impl/StatsUtil.java 2008-06-04 02:51:14 UTC (rev 10098) > +++ xwiki-platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > stats/impl/StatsUtil.java 2008-06-04 02:52:41 UTC (rev 10099) > @@ -590,7 +590,7 @@ > cookie.setMaxAge(time); > > String cookieDomain = null; > - String[] cookieDomains = StatsUtil.getCookieDomains(context); > + getCookieDomains(context); btw this is a badly named method if it has some side effects other than getting cookie domains... -Vincent > > if (cookieDomains != null) { > String servername = context.getRequest().getServerName(); > for (int i = 0; i < cookieDomains.length; i++) {

1 0

Re: [xwiki-devs] [xwiki-notifications] r10097 - xwiki-platform/xwiki-tools/trunk/xwiki-verification-resources/src/main/resources
by Vincent Massol 04 Jun '08

04 Jun '08

I remember why it was 98 and not 100 below for Eclipse. That's because with 100 sometimes it failed to cut the line at 100 and went beyond it. Let's see what it does now. Thanks -Vincent On Jun 4, 2008, at 4:32 AM, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2008-06-04 04:32:10 +0200 (Wed, 04 Jun 2008) > New Revision: 10097 > > Modified: > xwiki-platform/xwiki-tools/trunk/xwiki-verification-resources/src/ > main/resources/checkstyle.xml > xwiki-platform/xwiki-tools/trunk/xwiki-verification-resources/src/ > main/resources/codestyle-eclipse.xml > xwiki-platform/xwiki-tools/trunk/xwiki-verification-resources/src/ > main/resources/codestyle-idea.xml > Log: > XTVERIFICATIONS-3: Increase the maximum line length in java source > files to 120 > Done. > > > Modified: xwiki-platform/xwiki-tools/trunk/xwiki-verification- > resources/src/main/resources/checkstyle.xml > =================================================================== > --- xwiki-platform/xwiki-tools/trunk/xwiki-verification-resources/ > src/main/resources/checkstyle.xml 2008-06-04 01:27:17 UTC (rev 10096) > +++ xwiki-platform/xwiki-tools/trunk/xwiki-verification-resources/ > src/main/resources/checkstyle.xml 2008-06-04 02:32:10 UTC (rev 10097) > @@ -200,8 +200,8 @@ > </module> > > <module name="LineLength"> > - <property name="ignorePattern" value="(@version|@see| > ^import)"/> > - <property name="max" value="100"/> > + <property name="ignorePattern" value="(@version|@see|@link| > ^import)"/> > + <property name="max" value="120"/> > </module> > > <module name="LocalFinalVariableName"/> > > Modified: xwiki-platform/xwiki-tools/trunk/xwiki-verification- > resources/src/main/resources/codestyle-eclipse.xml > =================================================================== > --- xwiki-platform/xwiki-tools/trunk/xwiki-verification-resources/ > src/main/resources/codestyle-eclipse.xml 2008-06-04 01:27:17 UTC > (rev 10096) > +++ xwiki-platform/xwiki-tools/trunk/xwiki-verification-resources/ > src/main/resources/codestyle-eclipse.xml 2008-06-04 02:32:10 UTC > (rev 10097) > @@ -70,7 +70,7 @@ > <setting > id > = > "org > .eclipse > .jdt > .core > .formatter > .insert_space_before_opening_angle_bracket_in_type_parameters" > value="do not insert"/> > <setting > id > = > "org > .eclipse > .jdt.core.formatter.insert_new_line_in_empty_type_declaration" > value="insert"/> > <setting > id > = > "org > .eclipse > .jdt.core.formatter.comment.clear_blank_lines_in_block_comment" > value="true"/> > -<setting id="org.eclipse.jdt.core.formatter.lineSplit" value="98"/> > +<setting id="org.eclipse.jdt.core.formatter.lineSplit" value="120"/> > <setting > id > = > "org > .eclipse.jdt.core.formatter.insert_space_before_opening_paren_in_if" > value="insert"/> > <setting > id > = > "org > .eclipse > .jdt > .core > .formatter.insert_space_between_brackets_in_array_type_reference" > value="do not insert"/> > <setting > id > = > "org > .eclipse > .jdt > .core > .formatter > .insert_space_after_opening_paren_in_parenthesized_expression" > value="do not insert"/> > @@ -184,7 +184,7 @@ > <setting > id > = > "org > .eclipse > .jdt.core.formatter.insert_new_line_before_while_in_do_statement" > value="do not insert"/> > <setting > id > = > "org > .eclipse > .jdt.core.formatter.alignment_for_arguments_in_enum_constant" > value="20"/> > <setting > id="org.eclipse.jdt.core.formatter.comment.format_javadoc_comments" > value="true"/> > -<setting id="org.eclipse.jdt.core.formatter.comment.line_length" > value="100"/> > +<setting id="org.eclipse.jdt.core.formatter.comment.line_length" > value="120"/> > <setting > id > ="org.eclipse.jdt.core.formatter.blank_lines_between_import_groups" > value="1"/> > <setting > id > = > "org > .eclipse > .jdt > .core > .formatter.insert_space_before_comma_in_enum_constant_arguments" > value="do not insert"/> > <setting > id="org.eclipse.jdt.core.formatter.insert_space_before_semicolon" > value="do not insert"/> > > Modified: xwiki-platform/xwiki-tools/trunk/xwiki-verification- > resources/src/main/resources/codestyle-idea.xml > =================================================================== > --- xwiki-platform/xwiki-tools/trunk/xwiki-verification-resources/ > src/main/resources/codestyle-idea.xml 2008-06-04 01:27:17 UTC (rev > 10096) > +++ xwiki-platform/xwiki-tools/trunk/xwiki-verification-resources/ > src/main/resources/codestyle-idea.xml 2008-06-04 02:32:10 UTC (rev > 10097) > @@ -34,7 +34,7 @@ > <option name="BLANK_LINES_AROUND_FIELD" value="1" /> > <option name="CLASS_COUNT_TO_USE_IMPORT_ON_DEMAND" value="99" /> > <option name="NAMES_COUNT_TO_USE_IMPORT_ON_DEMAND" value="99" /> > - <option name="RIGHT_MARGIN" value="100" /> > + <option name="RIGHT_MARGIN" value="120" /> > <option name="CALL_PARAMETERS_WRAP" value="1" /> > <option name="METHOD_PARAMETERS_WRAP" value="1" /> > <option name="EXTENDS_LIST_WRAP" value="1" />

1 0

Re: [xwiki-devs] [xwiki-notifications] r10096 - xwiki-platform/core/trunk/xwiki-velocity/src/main/java/org/xwiki/velocity
by Vincent Massol 04 Jun '08

04 Jun '08

Hi Sergiu, Thanks for fixing my javadoc :) However our automated refactoring has some shortcomings which I've pointed below. I don't know if we can improve the IDE configuration but it would be nice to try since it generates some code that is less readable than the one we generate by hand. [snip] On Jun 4, 2008, at 3:27 AM, sdumitriu (SVN) wrote: [snip] > -public class DefaultVelocityContextFactory extends AbstractLogEnabled > - implements VelocityContextFactory, Initializable, Composable > +public class DefaultVelocityContextFactory extends > AbstractLogEnabled implements > + VelocityContextFactory, Initializable, Composable IMO it's better to keep implements on the same line as the interfaces it implements and not break it. > // Instantiate Velocity tools > if (this.properties != null) { > - for (Enumeration< ? > props = > this.properties.propertyNames(); > - props.hasMoreElements();) > - { > + for (Enumeration< ? > props = > this.properties.propertyNames(); props > + .hasMoreElements();) { This is way less readable than the version I had. Also remember that we agreed to use a curly brace on the next line for this case (i.e. when the conditions wraps). In addition I don't like how props.hasMoreElements() is cut. > // Call all components implementing the > VelocityContextInitializer's role. > try { > - for (Object interceptor > - : > this.componentManager.lookupList(VelocityContextInitializer.ROLE)) > - { > + for (Object interceptor : this.componentManager > + .lookupList(VelocityContextInitializer.ROLE)) { > ((VelocityContextInitializer) > interceptor).initialize(context); > } same here for the curly brace. > // Ensure that initialization has been called > if (this.engine == null) { > - throw new XWikiVelocityException("This Velocity Engine > has not yet been initialized. " > - + " You must call its initialize() method before > you can use it."); > + throw new XWikiVelocityException( > + "This Velocity Engine has not yet been initialized. " > + + " You must call its initialize() method > before you can use it."); I think my version is better and takes only 2 lines.

1 0

[xwiki-devs] [proposal] Change the maximum line width in the codestyle to 128 characters
by Sergiu Dumitriu 04 Jun '08

04 Jun '08

Hi devs, Vincent said that he wanted to propose increasing the maximum line width for a while, but didn't get to do it yet. And since I want the same thing, I'm writing the proposal. So, the idea is to increase the line width to 128 (or 120? I like 128 better), since: - nice code uses descriptive variable/method names, which tend to be quite long, so many method calls span 2 or more lines - we're past the stage where developers have small displays that can only display 80 (or 100) characters at a time - right now the eclipse settings are at 98 chars, which is quite a silly number, and changing to only 100 is not worth the effort, so while we're increasing it, we can use a larger value Migration plan: - first, change the xwiki-verification-tools (next Tuesday) - we don't want to do a massive update, since it will probably create conflicts with the local changes for each developer, and break existing patches - whenever someone changes a file, he should first do a cleanup and commit the file without code changes, then a second commit with the actual behavior fix - never mix cosmetic changes with actual code affecting the behavior, as it will be hard to review that change - the copyright notice doesn't need to be updated So, everybody agrees? Do we use 120 or 128? -- Sergiu Dumitriu http://purl.org/net/sergiu/

4 5

[xwiki-devs] should xwiki revert the attachment name
by Wang Ning 03 Jun '08

03 Jun '08

Hi, First, I upload a file named "the open grid service architecture.pdf" to xwiki page. Then I download it from the page. The default target file name change to "theopengridservicearchitecture.pdf" which is not friendly file name. I wonder if we can improve this. Are there big difficulties with attachment store components to do so? Thanks. -- Sincerely, Wang Ning

1 0

[xwiki-devs] xwiki dev best practices page problem
by Vincent Massol 03 Jun '08

03 Jun '08

Hi all, I see that Ludovic has started this page http://platform.xwiki.org/xwiki/bin/view/DevGuide/Best+Practices+XWiki+Appl… However I think it should be moved to the Draft area. Right now it's very misleading and readers will think that it represents best practices that the xwiki dev team is recommending while it's not. It'll become those when we agree on them and that hasn't been done AFAIK. We could move it to the Draft area or we could start a vote on its content... WDYT? Thanks -Vincent

5 4

[xwiki-devs] "List of Groups" property error
by shivshan 03 Jun '08

03 Jun '08

Hi If i try to add a property of type "List of Groups", i get the followng error. Is this a known issue? XWiki XE 1.4 running on Windows XP. Thanks, Shiva A problem occured while trying to service your request. Please contact the support if this happens again. Detailed information: Error number 0 in 11: Uncaught exception Wrapped Exception: com.xpn.xwiki.objects.meta.GroupsMetaClass com.xpn.xwiki.XWikiException: Error number 0 in 11: Uncaught exception Wrapped Exception: com.xpn.xwiki.objects.meta.GroupsMetaClass at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:230) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:616) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) at org.mortbay.http.HttpContext.handle(HttpContext.java:1565) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) at org.mortbay.http.HttpContext.handle(HttpContext.java:1517) at org.mortbay.http.HttpServer.service(HttpServer.java:954) at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:983) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) Wrapped Exception: java.lang.ClassCastException: com.xpn.xwiki.objects.meta.GroupsMetaClass at com.xpn.xwiki.web.PropAddAction.action(PropAddAction.java:56) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:204) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:616) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) at org.mortbay.http.HttpContext.handle(HttpContext.java:1565) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) at org.mortbay.http.HttpContext.handle(HttpContext.java:1517) at org.mortbay.http.HttpServer.service(HttpServer.java:954) at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:983) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) -- View this message in context: http://www.nabble.com/%22List-of-Groups%22-property-error-tp17574276p175742… Sent from the XWiki- Dev mailing list archive at Nabble.com.

2 3

[xwiki-devs] [Proposal] Introduce new Execution Context module
by Vincent Massol 03 Jun '08

03 Jun '08

Hi, I've been thinking a lot about the Container component I introduced and while writing unit tests for some of the new rendering classes I realized there was something not right: it's not normal that the HTML exporter or the rendering module depend on the Container object, and especially on the Request. Thus I'd like to introduce the notion of Execution Context (EC in short). The idea is that the xwiki entry points depend on the environment (Servlet, Portlet, etc) but those entry points create an Execution Context which is then used by the core components, independently of the environment. For example the VelocityContext is now put in the EC and not in the Request object. The Container objects still exist and can be used where required but it's expected that they should not be used since that makes the code dependent on the environment. This solves issue I had with code that don't have a request. I have it done on my machine. WDYT? Ok to commit? Thanks -Vincent PS: BTW this makes it very similar to the current XWikiContext (which is good) with the exception that the Container objects are not located inside the EC but as separate threadsafe variables.

3 5

[xwiki-devs] Openoffice sdk client need openoffice runtime to run
by Wang Ning 03 Jun '08

03 Jun '08

Hi, I want to develop a component to handle office documents in xwiki. As we discussion before, I want to use openoffice api. I set a openoffice develop environment in my pc running ubuntu 8.04, and learn how to use openoffice api. Yes, The oo sdk is powerful to address office documents, MS doc, MS excel... But there's a problem. AFAIK, openoffice api need a openoffice local runtime or a remote server running openoffice. The whole openoffice runtime is 356M, more or less, so we shouldn't contain it in xwiki release. Hense, I think if we want the office importer run in a computer, the computer should have installed openoffice or configurate a remote openoffice server. WDYT? I need some suggestion. Thanks. -- Sincerely, Wang Ning

5 7

[xwiki-devs] Problem in Snippets space on code.xwiki.org
by shivshan 03 Jun '08

03 Jun '08

Hi Clicking on any snippet gives a blank page with the error "Topic XWiki.SnippetClassSheet does not exist". Regards, Shiva -- View this message in context: http://www.nabble.com/Problem-in-Snippets-space-on-code.xwiki.org-tp1762259… Sent from the XWiki- Dev mailing list archive at Nabble.com.

1 0

[xwiki-devs] XWS 1.1 status and new dates
by Jerome Velociter 03 Jun '08

03 Jun '08

Hello devs, XWS 1.1 M2 was originally planned for May 26th. Unfortunately, I have been taken by other projects and could not stick to that date. I give you here a status on what needs to be achieved and new dates proposal. For me, the consequent tasks left to be done for us to be feature closed for M2 are the following: * XWS-7 (Manage groups of administrators & power users). It has been started by Florin. For me it's 80% complete today. Florin will continue to work on it. * XWS-79 (Invitation management). About 50% complete. * XWS-23 Support public registration As for dates, here is my proposal : * 1.1 M2 next Monday (June 9th) * 1.1 RC1 on June 19th * 1.1 RC2 or 1.1 final on June 30th. wdyt ? Regards, Jerome.

3 2

[xwiki-devs] XWiki-2006 again (configurable database schema name)
by rssh 03 Jun '08

03 Jun '08

Good day community. I want to ask again about XWIKI-2006 issue. http://jira.xwiki.org/jira/browse/XWIKI-2006 Now I find the way to change initialization of hibernate (instead calling of setDatabase in the beginning of each session) for non-virtual mode. [attached as configurated_db_schema_07.patch] Can I ask committers to review one ? (See previous discussion in this mail list http://markmail.org/message/6mtyxwff4ccmn3lk) We have 2 votes for previous patch. We need three [as I remember rules of this game] -- yet one vote, please ;) -- Ruslan Shevchenko GradSoft. http://www.gradsoft.ua

1 0

Re: [xwiki-devs] [xwiki-notifications] r10078 - xwiki-products/xwiki-enterprise/branches/xwiki-enterprise-1.4/distribution-test/selenium-tests/src/test/it/com/xpn/xwiki/it/selenium
by Vincent Massol 02 Jun '08

02 Jun '08

Hi Ludovic, You should gather those 3 methods into one: * functional tests are slow to run and this will slow down the overall tests (the setup is long) * the naming of the test methods is not explanatory Thanks -Vincent On Jun 2, 2008, at 3:39 PM, ludovic (SVN) wrote: > Author: ludovic > Date: 2008-06-02 15:39:10 +0200 (Mon, 02 Jun 2008) > New Revision: 10078 > > Modified: > xwiki-products/xwiki-enterprise/branches/xwiki-enterprise-1.4/ > distribution-test/selenium-tests/src/test/it/com/xpn/xwiki/it/ > selenium/WysiwygEditorFromWikiTest.java > Log: > XWIKI-2343 Wysiwyg editor breaks accents in links > > Modified: xwiki-products/xwiki-enterprise/branches/xwiki- > enterprise-1.4/distribution-test/selenium-tests/src/test/it/com/xpn/ > xwiki/it/selenium/WysiwygEditorFromWikiTest.java > =================================================================== > --- xwiki-products/xwiki-enterprise/branches/xwiki-enterprise-1.4/ > distribution-test/selenium-tests/src/test/it/com/xpn/xwiki/it/ > selenium/WysiwygEditorFromWikiTest.java 2008-06-01 21:50:23 UTC (rev > 10077) > +++ xwiki-products/xwiki-enterprise/branches/xwiki-enterprise-1.4/ > distribution-test/selenium-tests/src/test/it/com/xpn/xwiki/it/ > selenium/WysiwygEditorFromWikiTest.java 2008-06-02 13:39:10 UTC (rev > 10078) > @@ -100,4 +100,29 @@ > clickLinkWithText("Wiki"); > assertEquals("## comment", getFieldValue("content")); > } > + > + public void testAccentsInLinks() throws Exception > + { > + setFieldValue("content", "[\u00E9t\u00E9]"); > + clickLinkWithText("WYSIWYG"); > + clickLinkWithText("Wiki"); > + assertEquals("[\u00E9t\u00E9]", getFieldValue("content")); > + } > + > + public void testAccentsInLinks2() throws Exception > + { > + setFieldValue("content", "[test>\u00E9t\u00E9]"); > + clickLinkWithText("WYSIWYG"); > + clickLinkWithText("Wiki"); > + assertEquals("[test>\u00E9t\u00E9]", > getFieldValue("content")); > + } > + > + public void testAccentsInLinks3() throws Exception > + { > + setFieldValue("content", "[\u00E9t\u00E9>test]"); > + clickLinkWithText("WYSIWYG"); > + clickLinkWithText("Wiki"); > + assertEquals("[\u00E9t\u00E9>test]", > getFieldValue("content")); > + } > + > }

1 0

[xwiki-devs] [proposal] Componentize XWiki Stores
by Artem Melentyev 02 Jun '08

02 Jun '08

Hi devs. I would like to propose: 1. Make all xwiki stores as components. So they will be constructed via our ComponentManager. 2. Deprecate all store public constructors. Because they are useless for components. 3. Add SessionFactory component to all hibernate stores. this will fix XWIKI-2332: Share one session factory among all hibernate stores. move all hibernate configuration to SessionFactory component. one SessionFactory is shared by all stores by default (configured in components.xml). here is tentative interface SessionFactory { Session openSession() Configuration getConfiguration() /** rebuild session factory with new configuration. needed for inject hibernate custom mappings. */ void updateConfiguration(Configuration cfg) } 4. Add QueryManager component to main store (XWikiStoreInterface) WDYT? -- Artem Melentyev

1 0

[xwiki-devs] [VOTE] Release XEM 1.3M1
by Thomas Mortagne 02 Jun '08

02 Jun '08

Hi, As XE 1.5M1 is now released, I would like to released XEM 1.3M1 based on it after XEM 1.2 final release. The pure XEM modification part is the same as XEM 1.2 final but with all new XE 1.5 branch features. See http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXEM13M1 Here is my +1 -- Thomas Mortagne

3 2

[xwiki-devs] XWiki Enterprise 1.4.1 to be released ASAP
by Jean-Vincent Drean 02 Jun '08

02 Jun '08

Hi XWikiers, XWiki Enterprise 1.4 has introduced a regression for group management in farm mode. We strongly suggest to use XWiki Enterprise 1.3.2 if you are upgrading a wiki farm before the 1.4.1 release. XWiki Enterprise 1.4.1 is planned on june 2nd and will be performed by Thomas Mortagne, it will include the following fixes : * XWIKI-2413 : Global groups are not taken into account in a virtual wiki Anything missing in the list ? Thanks, -- Jean-Vincent Drean

6 9

[xwiki-devs] [ANN] XWiki Enterprise 1.5 Milestone 1 Released
by Jean-Vincent Drean 02 Jun '08

02 Jun '08

The XWiki development team is pleased to announce the release of XWiki Enterprise 1.5 Milestone 1. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download First milestone of the XWiki Enterprise 1.5 version. Main changes: * LDAP support improvements ** Add possibility to map one LDAP group with more that one XWiki group ** Add the ability to configure LDAP groups classes and members fields names ** LDAP authenticator re-save user page even there is no modification ** "userPassword" LDAP field should be configurable ** Makes the SSL provider implementation used to support LDAP communication over SSL configurable ** LDAP authentication print error message with empty "group_mapping" property * Better PDF export support * Have "from" (second to last version) and "to" (last version) fields checked by default in the the document history * Ability to change just one (or several) object properties * Automatic logging of deprecated method calls in Velocity * Better language negotiation * Don't display the login link on the login page Note that the general goals of XE 1.5 are : * More bug fixes * Better performance * More automated tests * Overhaul of the Administration For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise15M1 Thanks, The XWiki dev team

1 0

[xwiki-devs] best way to override xwiki.cfg properties in my source?
by Paul Libbrecht 02 Jun '08

02 Jun '08

Hello list, as indicated on: http://www.nabble.com/my-attempt-at-building-a-development-curriki-to175692… I am using a simple maven install to build curriki which is very nice. Within the process both xwiki.cfg and hibernate.cfg.xml are built and I could override these with changes in the pom.xml. Do I have a chance to override these somewhere else? thanks in advance paul

2 1

[xwiki-devs] Google AJAX Libraries API
by Fabio Mancinelli 01 Jun '08

01 Jun '08

Hi all, Maybe this can be interesting... http://code.google.com/apis/ajaxlibs/ Cheers, Fabio

5 4

[xwiki-devs] Watch Menu in XE 1.4
by Glenn Everitt 01 Jun '08

01 Jun '08

I wasn't seeing the watch menu in XE 1.4. In menuview.vm an additional test was added: && $wiki.exists("XWiki.WatchListManager") I don't seem to have the page and so the menu doesn't appear. Does something have to be separately installed? If I remove the test above the Watch Menu is displayed as expected. I am not using virtual Wiki's. Is the test necessary? Glenn Everitt -- View this message in context: http://www.nabble.com/Watch-Menu-in-XE-1.4-tp17581949p17581949.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

2 1