xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] [VOTE] Dates for XE 3.2 Release

by Vincent Massol

Hi devs, I forgot to propose dates in the Roadmap mail for XE 3.2 so here's a proposal: 3.2M1: 18 July 2011 3.2M2: 15 August 2011 3.2M3: 12 Sep 2011 3.2RC1: 26 Sep 2011 3.2 Final: 10 Oct 2011 Rationale: - 4 week for milestone releases - 2 weeks for RC and Final - 1 more milestone than usual since it's holiday time and most committers will be off at least 2 to 4 weeks during the summer Here's my +1 Thanks -Vincent

14 years

[xwiki-devs] creating groups via XML-RPC

by Riveira Faraldo, Bernardo

Hi there! We are trying to use XWiki 3.0 enterprise, trying to create via XML-RPC thousands of users, groups and membership programmatically so we can keep updated AD, Liferay, other sources of users, other apps, all with CAS integration, etc. As there is still no confluence 2.0 API compatibility but we need to create users & groups in XWiki from an external software, we have been collecting pieces of code from messages and FAQs about how to implement it. We try to create users, their pages, and add them to the XWikiAllGroup with : Page page = new Page(); page.setSpace("XWiki"); page.setTitle("username01"); page.setId("XWiki.username01"); page.setContent("{{include document=\"XWiki.XWikiUserSheet\"/}}"); rpc.storePage(page); XWikiObject xobj = new XWikiObject(); xobj.setClassName("XWiki.XWikiUsers"); xobj.setPageId("XWiki.username01"); xobj.setProperty("first_name", "name"); xobj.setProperty("last_name", "last name"); xobj.setProperty("email", "email(a)email.com"); xobj.setProperty("password","##########"); rpc.storeObject(xobj); XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("XWiki.XWikiAllGroup"); xobjgrp.setProperty("member","XWiki.username01"); rpc.storeObject(xobjgrp); (Suppose we run that with username01 to username99) Although first time we run this, the page gets created, the user gets created but the properties not! :-o If we run again the import, then every user gets their properties. :-? Then, only the LAST user created gets correctly added to XWiki.XWikiAllGroup. If we stop/debug the program between each user creation process, always the last one appears at XWiki.XWikiAllGroup when checking via UI. So they are all there for a moment, until they are replaced by the last one. Like if the rpc.storeObject(xobjgrp) deleted previously any other user in that XWiki.XWikiAllGroup page. Then we try to create groups using this: // create group 01 Page page = new Page(); page.setSpace("XWiki"); page.setTitle("group01"); page.setContent("{{include document='XWiki.XWikiGroupSheet' /}}"); rpc.storePage(page); // create group 02 Page page = new Page(); page.setSpace("XWiki"); page.setTitle("group02"); page.setContent("{{include document='XWiki.XWikiGroupSheet' /}}"); rpc.storePage(page); ... Those "Groups" get created as Pages with XWikiGroupSheet app that allows us to see/edit the users via UI, but we need to add them via XML-RPC. ALSO, they are Pages, but they are NOT EXACTLY the same as if they where created via the Admin UI, where when you create a "Group" it shows slightly differently: Autocreated via XML-RPC: Versus when a group is created via Admin UI, it shows up differently, just like this: SO, we suppose the way we create a Group via XML-RPC (just a Page with a special Sheet) is NOT ENOUGH. And finally we try to add existing users to newly created groups with code like this: // user 01 to group 01 XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("group01"); xobjgrp.setProperty("member","XWiki.username01"); rpc.storeObject(xobjgrp); // user 01 to group 02 XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("group02"); xobjgrp.setProperty("member","XWiki.username01"); rpc.storeObject(xobjgrp); // user 02 to group 01 XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("group01"); xobjgrp.setProperty("member","XWiki.username02"); rpc.storeObject(xobjgrp); // user 03 to group 01 XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("group01"); xobjgrp.setProperty("member","XWiki.username02"); rpc.storeObject(xobjgrp); ... If now we check the group via UI, we can find Pages named XWiki.group01 , XWiki.group02, and with only one user each (although in the code up there username 01, 02 and 03 should be members of group01 !!! only THE LAST ONE (username03) remains. Also we tried to add also some users to the default (pre-created) XWiki.XWikiAdminGroup so they can act as administrators: XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("XWiki.XWikiAdminGroup"); xobjgrp.setProperty("member","XWiki.username01"); rpc.storeObject(xobjgrp); XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("XWiki.XWikiAdminGroup"); xobjgrp.setProperty("member","XWiki.username02"); rpc.storeObject(xobjgrp); As before only XWiki.username02 stays as member of XWiki.XWikiAdminGroup. We tried this with a fresh install of XWikiEnt3.0+Jetty+HSQLDB, then in Tomcat+MySQL, same problem in all of them. So, are we doing something wrong? Maybe something must be done with every user or group before you can add membership via XML-RPC? Sorry for the long post and thanks in advance! Bernardo Riveira Hi there! We are trying to use XWiki 3.0 enterprise, trying to create via XML-RPC thousands of users, groups and membership programmatically so we can keep updated AD, Liferay, other sources of users, other apps, all with CAS integration, etc. As there is still no confluence 2.0 API compatibility but we need to create users & groups in XWiki from an external software, we have been collecting pieces of code from messages and FAQs about how to implement it. We try to create users, their pages, and add them to the XWikiAllGroup with : Page page = new Page(); page.setSpace("XWiki"); page.setTitle("username01"); page.setId("XWiki.username01"); page.setContent("{{include document=\"XWiki.XWikiUserSheet\"/}}"); rpc.storePage(page); XWikiObject xobj = new XWikiObject(); xobj.setClassName("XWiki.XWikiUsers"); xobj.setPageId("XWiki.username01"); xobj.setProperty("first_name", "name"); xobj.setProperty("last_name", "last name"); xobj.setProperty("email", "email(a)email.com"); xobj.setProperty("password","##########"); rpc.storeObject(xobj); XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("XWiki.XWikiAllGroup"); xobjgrp.setProperty("member","XWiki.username01"); rpc.storeObject(xobjgrp); (Suppose we run that with username01 to username99) Although first time we run this, the page gets created, the user gets created but the properties not! :-o If we run again the import, then every user gets their properties. :-? Then, only the LAST user created gets correctly added to XWiki.XWikiAllGroup. If we stop/debug the program between each user creation process, always the last one appears at XWiki.XWikiAllGroup when checking via UI. So they are all there for a moment, until they are replaced by the last one. Like if the rpc.storeObject(xobjgrp) deleted previously any other user in that XWiki.XWikiAllGroup page. Then we try to create groups using this: // create group 01 Page page = new Page(); page.setSpace("XWiki"); page.setTitle("group01"); page.setContent("{{include document='XWiki.XWikiGroupSheet' /}}"); rpc.storePage(page); // create group 02 Page page = new Page(); page.setSpace("XWiki"); page.setTitle("group02"); page.setContent("{{include document='XWiki.XWikiGroupSheet' /}}"); rpc.storePage(page); ... Those "Groups" get created as Pages with XWikiGroupSheet app that allows us to see/edit the users via UI, but we need to add them via XML-RPC. ALSO, they are Pages, but they are NOT EXACTLY the same as if they where created via the Admin UI, where when you create a "Group" it shows slightly differently: Autocreated via XML-RPC: [cid:image001.png@01CC2C45.659F3540] Versus when a group is created via Admin UI, it shows up differently, just like this: [cid:image002.png@01CC2C45.659F3540] SO, we suppose the way we create a Group via XML-RPC (just a Page with a special Sheet) is NOT ENOUGH. And finally we try to add existing users to newly created groups with code like this: // user 01 to group 01 XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("group01"); xobjgrp.setProperty("member","XWiki.username01"); rpc.storeObject(xobjgrp); // user 01 to group 02 XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("group02"); xobjgrp.setProperty("member","XWiki.username01"); rpc.storeObject(xobjgrp); // user 02 to group 01 XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("group01"); xobjgrp.setProperty("member","XWiki.username02"); rpc.storeObject(xobjgrp); // user 03 to group 01 XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("group01"); xobjgrp.setProperty("member","XWiki.username02"); rpc.storeObject(xobjgrp); ... If now we check the group via UI, we can find Pages named XWiki.group01 , XWiki.group02, and with only one user each (although in the code up there username 01, 02 and 03 should be members of group01 !!! only THE LAST ONE (username03) remains. Also we tried to add also some users to the default (pre-created) XWiki.XWikiAdminGroup so they can act as administrators: XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("XWiki.XWikiAdminGroup"); xobjgrp.setProperty("member","XWiki.username01"); rpc.storeObject(xobjgrp); XWikiObject xobjgrp = new XWikiObject(); xobjgrp.setClassName("XWiki.XWikiGroups"); xobjgrp.setPageId("XWiki.XWikiAdminGroup"); xobjgrp.setProperty("member","XWiki.username02"); rpc.storeObject(xobjgrp); As before only XWiki.username02 stays as member of XWiki.XWikiAdminGroup. We tried this with a fresh install of XWikiEnt3.0+Jetty+HSQLDB, then in Tomcat+MySQL, same problem in all of them. So, are we doing something wrong? Maybe something must be done with every user or group before you can add membership via XML-RPC? Sorry for the long post and thanks in advance! Bernardo Riveira ***** Este mensaje se dirige exclusivamente a su destinatario. Puede contener información privilegiada, confidencial o legalmente protegida. Si ha recibido este mensaje por error le rogamos que lo borre inmediatamente, así como todas sus copias, y lo comunique al remitente. En virtud de la legislación vigente está prohibida la utilización, divulgación copia o impresión sin autorización. No existe renuncia a la confidencialidad o privilegio por causa de una transmisión errónea. *****

14 years

[xwiki-devs] [Proposal] Create 'xwiki' database on first run if it does not exist

by Eduard Moraru

Hi, I think this is a common and long living problem. Some more feedback/points of view on this might be welcomed. http://jira.xwiki.org/jira/browse/XWIKI-6715 Thanks, Eduard

14 years

[xwiki-devs] [VOTE] Remove automatic plugin reinit when XWikiPreference is modified

by Thomas Mortagne

Hi dev, Currently each time you modify XWikiPreference all the plugin are reloaded and reinitialized. This is very bad so I would like to remove this. Also this is done only when not in vistual mode (what the...). If either a plugin cache something coming from XWikiPreference it should register to event itself and update its cache when needed. I don't know any plugin which actually count on this "feature". My proposal is to simply remove this code which is useless and does not even work in virtual mode anyway. WDYT ? Here is my +1 -- Thomas Mortagne

14 years

[xwiki-devs] Status: Xwiki Android Client

by Chamika Weerasinghe

Hi, For now I added Wiki and Space and the Search access in xwiki-android-rest via handling JSON objects. I commited new files to repo. When I implementing access to Page resources I found that Xwiki REST sends different contents in XML and JSON For example XML content http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/Blog/pages/BlogIntroduc… is different from JSON content http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/Blog/pages/BlogIntroduc… Because of this difference I decided to deserialize XML instead of JSON. (I must modify all the class files for this). XWiki RESTful API doc ( http://platform.xwiki.org/xwiki/bin/view/Features/XWikiRESTfulAPI) describes XML -> Java conversion by using "org.apache.commons.httpclient". But this library seems to be larger in size. As Thomas said size does matter in Android. Therefore I decided to use "org.apache.http" which built in Android. But I got following error 06-12 20:02:55.070: WARN/dalvikvm(650): VFY: unable to resolve static method 1169: Ljavax/xml/bind/JAXBContext;.newInstance (Ljava/lang/String;)Ljavax/xml/bind/JAXBContext; Can anybody suggest me what causes this error? Best Regards, Chamika Weerasinghe

14 years

[xwiki-devs] [VOTE] Build Manager duty

by Vincent Massol

Hi committers, We're having a hard time stabilizing our build (especially the functional test part, see my previous mail entitled "[VOTE] Important: Strategy to fix failing tests and stability"). Now I believe that it's going to be hard to enforce it and thus I'd like to propose a variation: * The Build Manager has the *responsibility* to get the build fixed ASAP whenever it's failing. His priority #1 during the week becomes monitoring the Build * By "Build" we mean the CI Build on ci.xwiki.org and by "failing" we mean anything that makes the build fail: tests, compilation, clirr, etc. * Every week we have a different Build Manager chosen amongst the Committers * In order to fix build issues the Build Manager has several possibilities: - find out who caused the build to break and ask that person to fix it. That person cannot refuse that and must consider it his/her priority to fix it (or rollback the change that caused the build to fail) - rollback the issue that caused the build to fail - fix it himself/herself - find someone knowledgable in the failing domain and get him/her to fix the build. * At the end of the Week the Build Manager hands over his duty to the next Build Manager by contacting him/her. * We create a Build Manager Roster page on dev.xwiki.org to log past Build Managers (and possibly future ones if some have expressed the wish to be the Build Manager for a specific week). * All committers must perform this duty and take turns Since I've started doing this this week, I propose to take this role for the current week. I'm also proposing to log Caleb has having been the Build Manager for the past week since he's done a lot to stabilize the build. If the vote is passed I'll log this on the Committership page as a Committer duty (I'll also cross reference it from the Build page). Here's my +1 Thanks -Vincent

14 years

Re: [xwiki-devs] Status

by 许凌志(Jamesxu)

I am working on this project all the days following your instructions we discussed before. And the mainly work I have done are following : (1). Set up the framework for auto-suggestion, including three parts: a).The main object XWiki.editors.AutoSuggestion which is the entry for trigger auto-suggestion functions b).XWiki.editors.AutoSuggestion.Suggestor, which is only for wiki editors, and the main function is give the right suggestions according to user input in different context of triggers. The suggestor includes: XWiki.editors.AutoSuggestion.LinkSuggestor, XWiki.editors.AutoSuggestion.ImageSuggestor and XWiki.editors.AutoSuggestion.MacroSuggestor. c).XWiki.editors.autoSuggestion.SuggestionList, whic is the used for initializing the suggestion box, there are three kinds of SuggestionList: XWiki.editors.autoSuggestion.LinkSuggestionList, XWiki.editors.autoSuggestion.ImageSuggestionList, XWiki.editors.autoSuggestion.MacroSuggestionList. (2). I finished the XWiki.editors.autoSuggestion.SuggestionList and XWiki.editors.autoSuggestion.LinkSuggestionList. include the related css, it is more like a widget, can be instantiated alone, so that it can be used in Wysiwyg editors (3). Finish part of the main object : XWiki.editors.AutoSuggestion(only for testing Link SuggestionList) (4). Working on the XWiki.editors.AutoSuggestion.Suggestor and XWiki.editors.AutoSuggestion.LinkSuggestor for wiki editors. I don't commit the code because it is only part of them, and some of them can not run properly right now, In my plan, I will commit tonight maybe the in the afternoon in your time zoon. Sorry for commit late, because start is hard, I will increase the commit times, after the first commit, it will be helpful for mentors to review the code On Mon, Jun 13, 2011 at 6:03 PM, Marius Dumitru Florea < mariusdumitru.florea(a)xwiki.com> wrote: > Hi James, > > Any progress on the GSoC project? Time is passing and I haven't seen any > commit from you. Asking for feedback is very important as it gives you the > guarantee that you're going in the right direction. For instance, I don't > know what you're working on currently. > > Thanks, > Marius > -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

14 years

[xwiki-devs] [Follow-up] New administration section for the WYSIWYG editor

by Marius Dumitru Florea

Hi devs, Following http://lists.xwiki.org/pipermail/devs/2010-November/021012.html I made some improvements and now I have this http://incubator.myxwiki.org/xwiki/bin/view/Improvements/WysiwygEditorConfig . I'd like to include it in XE 3.0. WDYT? Thanks, Marius

14 years

[xwiki-devs] Scalable XWiki on NoSQL (Cassandra )

by supun wickramasinghe

Hi Devs, I'm Pulasthi and currently working on the Scalable XWiki on NoSQL (Cassandra ) project with Caleb James DeLisle. i got involved with the project as a GSOC applicant but the project was not selected for GSOC. i thought of informing the devs about my progress. As the project needed to use the Todd Nines Datanucleus Cassandra plugin which was not capable of querying non indexed queries. As the first part of the project i was able to successfully add a patch[1] to this and made some changes after getting feedback from Caleb James. [1] .Datanucleus Cassandra plugin with patch - https://github.com/pulasthi/Datanucleus-Cassandra-Plugin -- Pulasthi Supun Undergraduate Dpt of Computer Science & Engineering University of Moratuwa

14 years

[xwiki-devs] [proposal] Release on the coming Tuesday -- Also any known blockers for release?

by Caleb James DeLisle

Since there has not been much change since The last release I think we can get largely back on track. I understand Monday is a holiday for a number of people so I would like to propose releasing on Tuesday. That means we will need to start testing ASAP and I would like to know now if anybody knows of an issue which is a blocker for the 3.1 release. Thanks Caleb

14 years

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs