xwiki-devs August 2007

xwiki-devs@xwiki.org

27 participants
88 discussions

by Sergiu Dumitriu

Hi, I'm starting the release for XWiki 1.1 RC1. It was planned for yesterday, but was delayed due to several reasons: no mailing lists, some uncommitted code, some unresolved important bugs... It was already tested yesterday, and no bugs were discovered. There should be another RC in a few days, fixing some installer problems and the eventual bugs that might block a final 1.1 release. Sergiu -- http://purl.org/net/sergiu _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

17 years, 3 months

[xwiki-devs] Fwd: Use Swizzle directly or use a facade (was Re: XEclipse 1.0M1 will only work for xwiki-core-1.1M4 (but not for xwiki-core-1.2-SNAPSHOT))

by Asiri Rathnayake

---------- Forwarded message ---------- From: Asiri Rathnayake <asiri.rathnayake(a)gmail.com> Date: Aug 29, 2007 1:33 AM Subject: Re: Use Swizzle directly or use a facade (was Re: XEclipse 1.0M1will only work for xwiki-core-1.1M4 (but not for xwiki-core-1.2-SNAPSHOT)) To: Vincent Massol <vincent(a)massol.net> Cc: Catalin Hritcu <catalin.hritcu(a)gmail.com>, XWiki Dev < xwiki-dev(a)objectweb.org>, Tharindu Jayasuriya <djtharindu(a)gmail.com>, Sergiu Dumitriu <sergiu.dumitriu(a)gmail.com> Hi All, With Catalin's patch we (Catalin & Myself worked together on this) were able to modify XEclipse to use swizzle underneath. XEclipse - XWiki object model is still preserved. For an example, IXWikiConnection, IXWikiSpace, IXWikiPage are all there but they delegate method calls to internal swizzle implementation rather than handling them ourselves. Currently we have XEclipse (modified to use swizzle) working against current xwiki trunk (not commited yet). Once we have make it work with XWiki 1.1, we'll commit it out (possibly by tomorrow). Thanks Catalin for all the help. - Asiri On 8/28/07, Vincent Massol <vincent(a)massol.net> wrote: > > Hi Catalin, > > A new healthy fight! :) > > See below. > > On Aug 27, 2007, at 10:32 PM, Catalin Hritcu wrote: > > [snip] > > >> Pros: > >> * A single way for all xwiki clients to connect to XWiki servers > >> * Less maintenance, less documentation, less work in general since > >> someone > >> else is developing swizzle :). This point only is huge. > >> > > I would not stress this. Actually I already worked quite a lot on > > improving swizzle so far and I think there are many other ways we will > > have to improve swizzle. What is nice about it was having a visible > > working project to start from, rather than implementing it from > > scratch. Having David to "guard" the source is just the cherry on top > > of the cake. > > You didn't spend even 1% of the time it took to create Swizzle as it > is today and if you think about how swizzle will evolve in the future > that percentage drops down to 0.01%. This is why I thought this > should be stressed out :) > > [snip] > > >> * If swizzle goes away or is abandonned then it'll be bad for > >> xwiki and we'd > >> need to support it/reintegrate it. > >> > > First, swizzle is open source so can't "go away", we can always > > continue to maintain it. > > That's harder than you think. Radeox went away and are we maintaining > it? Nope. Of course we can always say that it's because its > architecture was too limited, etc but had it been maintained its > architecture could have evolved too. The same would happen with > swizzle if it goes away IMO. But it's not only an issue of Swizzle > going away because it's abandoned. Imagine a competitor project > appears and it's better than swizzle for XWiki. How do we tell all > our users that they have to redo all their client code. We won't and > thus we probably won't move to this better project because we have > standardized on Swizzle. > > It's about having a stable client-side interface. > > I much prefer the approach where we define our model objects (we need > them anyway on the server so it may even be possible to share some of > them on the client - Not sure about this but it's a thought) and our > interfaces and we keep the implementation separate. I'm 100% for > implementing those interfaces with Swizzle. > > In addition we need to offer a XWiki-specific API so instead of > offering several remoting APIs I propose we offer only one. Then it's > up to the implementations to implement them. The confluence > implementation (using Swizzle) could throw NotImplementedException > for stuff it doesn't implement so that client code using it will be > 100% confluence-compatible if that's the user's desire. And we would > be able to have a single unified API that has all the XWiki-specific > stuff. > > > And if it ever goes abandoned how would this > > be any worse than what we have now? Now we have two "little-swizzle" > > implementations one of them was _already_ abandoned, and the other is > > very likely to grow into a full fledged "swizzle". Even if we have to > > maintain one swizzle it's a big gain over having to maintain many. > > See above. > > > > >> Actually this is a point that is > >> bothering me Catalin. I think we'd need our own object model and > >> expose that > >> as a component and then provide a default implementation using > >> swizzle > >> behind the hood. Same as what we're doing for everything. This > >> will also > >> make the API seamless WRT extra APIs we have for xwiki (like getting > >> objects, etc). > >> > > It is true that swizzle provides an implementation but not an > > interface. However, why can't we provide interfaces as part of the > > swizzle project ? Why can't we make swizzle more component-friendly by > > just changing it? Why would we need another XWiki-specific wrapper > > layer? > > Swizzle is not our project. We could become committers to it of > course but I assure you it's still going to be 100 times more > difficult to evolve Swizzle than to evolve XWiki code. For 2 reasons: > * We "own" XWiki. All committers on XWiki are interested by XWiki only. > * Swizzle has to stay generic and making a generic change is always > more difficult than making a specific change. The same applies to the > fact that Swizzle if confluence-specific. > > Regarding the confluence-specific, it bothers me that the only > remoting interface we're providing is confluence-specific and has > confluence written all over. I think we should offer a XWiki-specific > API and let the user choose the implementation he wants transparently > (confluence or not). > > > One advantage I see of improving swizzle rather than hiding it away is > > that this way we are guaranteed(!) to stay compatible with confluence > > on the common features. While if you start to develop wrappers on top > > of swizzle that may or may not be the case. > > We wouldn't loose this feature by using Swizzle as an implementation > of our API. > > >> So IMO: > >> * We shouldn't use swizzle directly > >> * We should develop our own client side Java Objects and API > >> *interface* for > >> people interacting with XWiki remotely. > >> > > Why can't interfaces be done inside the swizzle project ? Why should > > we try to hide swizzle away ? > > See above. > > >> - That API should be independent of the protocol used. > >> > > Swizzle is actually already independent of the protocol used. It could > > work with SOAP as well as XML-RPC if somebody went into the trouble to > > reimplement everything for SOAP. The interface would be the same and a > > client would not be able to tell any difference. > > Then all the best. We can benefit from that. > > >> - A default implementation should be done using swizzle. It'll > >> be mostly > >> empty and only call out swizzle objects/swizzle APIs > >> * XEClipse should be refactored to use this API > >> * This API should be developed using components and using the new > >> org.xwiki > >> namespace. > >> > > Why can't this be done in an interoperable fashion part of the swizzle > > project ? Why can't the namespace be org.codehaus.swizzle :) ? Isn't > > this "not-made-here" attitude? > > Yep and that's important IMO (see above). The strategy I'd like to > have for XWiki from now on is to develop components and provide XWiki > interface classes. The implementations can be done using whatever > external frameworks. > > >> WDYT? > >> > > I think that we have no good reason to hide swizzle away under more > > wrapper layers since _swizzle_is_a_wrapper_itself_, and I think that > > we can solve any modularity/componentization problems inside the > > swizzle project. > > See above again. > > Let's see what others say. > > Thanks > -Vincent > > _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

17 years, 3 months

[xwiki-devs] Mailing lists: svn notifications working again

by Vincent Massol

Hi, We had some issues with scm mails not making it to the new lists. It's now been fixed. However this means we've lost a few commit emails (the ones done this morning till now). Sorry about that. Thanks -Vincent _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

17 years, 3 months

Re: [xwiki-devs] Proposal: Breaking API changes in the XML-RPC implementation

by Marta Girdea

+1 On 8/28/07, Catalin Hritcu <catalin.hritcu(a)gmail.com> wrote: > Hello, > > In a previous message I explained that I will soon do breaking API > changes in the XML-RPC implementation, but I was not explicit enough > about. Here is what I plan to implement ASAP if everybody agrees: > > 1) Remove the ConfluenceRpcInterface interface. We have already > discussed about dropping xmlrpc dynamic proxies in favor of swizzle > and the advantages this brings. This would be the last step towards > dropping dynamic proxies, and would ensure that there is no confusion > for users (of course this will also be documented on xwiki.org). > > 2) Remove the domain objects in the xwiki xmlrpc package. Again, we > are already using the swizzle domain objects. The only thing we still > have to settle is whether we will do it directly or through a facade, > and whether this facade will be part of xwiki or part of swizzle, but > this is the subject of another discussion. > > 3) Remove XWikiRpcHandler and XWikiRpcInterface. They are an attempt > to implement the JSPWiki interface that was not put into practice so > far. Currently only 2 methods are implemented: getPage and getAllPages > which return a string and a list of strings respectively. Even if > fully implemented I don't think that the JSPWiki interface would be > useful, since we already have the confluence api which is much more > powerful. > > The other xwiki modules will probably not be affected by these > changes. Existing users of the removed classes and interfaces will > have to adapt their code. However, since we just went from an "almost > working" implementation of XML-RPC to a working one, I believe that > this is the best moment to clean things up and make everything more > maintainable for the future. > > WDYT? > > Regards, > Catalin > _______________________________________________ > 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

17 years, 3 months

Re: [xwiki-devs] [xwiki-notifications] Build XWiki Platform Web::Default (HSQLDB) #184 failed

by Vincent Massol

Sorry about that, I committed some pom modifications by error. I've now reverted it. Thanks -Vincent On Aug 28, 2007, at 5:51 PM, teamcity(a)xwiki.org wrote: > Build XWiki Platform Web::Default (HSQLDB) #184 failed > Agent: Default agent > Build results: http://teamcity.xwiki.org/viewLog.html? > buildId=2160&buildTypeId=bt4 > > Changes included (1 change) > ==================================================== > Change 4535 by vmassol (1 file): > Uncomment the buildnumber plugin which was commented out by error > > see more information about changed files: http://teamcity.xwiki.org/ > viewLog.html?tab=buildChangesDiv&buildId=2160&buildTypeId=bt4 > > > ====================================================================== > ====== > Configure email notifications: http://teamcity.xwiki.org/ > profile.html?init=1#notifications > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

17 years, 3 months

[xwiki-devs] Fwd: Re: [xwiki-dev] xwiki database backup

by Catalin Hritcu

---------- Forwarded message ---------- From: anujssharma86(a)yahoo.co.in <anujssharma86(a)yahoo.co.in> Date: Aug 28, 2007 4:38 PM Subject: Re: Re: [xwiki-dev] xwiki database backup To: catalin.hritcu(a)gmail.com Hi Catalin, I am able to take the database backup. But what's happening is when i am restoring it the attachments are showing in the database but its not showing in xwiki interface where i had actually stored it. Thanks, Anuj _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

17 years, 3 months

Re: [xwiki-devs] Proposal: Breaking API changes in the XML-RPC implementation

by Sergiu Dumitriu

+1 On 8/28/07, Catalin Hritcu <catalin.hritcu(a)gmail.com> wrote: > Hello, > > In a previous message I explained that I will soon do breaking API > changes in the XML-RPC implementation, but I was not explicit enough > about. Here is what I plan to implement ASAP if everybody agrees: > > 1) Remove the ConfluenceRpcInterface interface. We have already > discussed about dropping xmlrpc dynamic proxies in favor of swizzle > and the advantages this brings. This would be the last step towards > dropping dynamic proxies, and would ensure that there is no confusion > for users (of course this will also be documented on xwiki.org). > > 2) Remove the domain objects in the xwiki xmlrpc package. Again, we > are already using the swizzle domain objects. The only thing we still > have to settle is whether we will do it directly or through a facade, > and whether this facade will be part of xwiki or part of swizzle, but > this is the subject of another discussion. > > 3) Remove XWikiRpcHandler and XWikiRpcInterface. They are an attempt > to implement the JSPWiki interface that was not put into practice so > far. Currently only 2 methods are implemented: getPage and getAllPages > which return a string and a list of strings respectively. Even if > fully implemented I don't think that the JSPWiki interface would be > useful, since we already have the confluence api which is much more > powerful. > > The other xwiki modules will probably not be affected by these > changes. Existing users of the removed classes and interfaces will > have to adapt their code. However, since we just went from an "almost > working" implementation of XML-RPC to a working one, I believe that > this is the best moment to clean things up and make everything more > maintainable for the future. > > WDYT? > > Regards, > Catalin Sergiu -- http://purl.org/net/sergiu _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

17 years, 3 months

[IMPORTANT] Mailing lists migration

by Vincent Massol

Hi everyone, We're currently undergoing mailing lists migration. As you've observed we've had some issues in the past and we're setting up a new mailing list server and new lists. We're automatically existing subscribers so you won't have anything to do. You'll just need to use the new lists when they're up. We'll send more information real soon. Thanks -Vincent

17 years, 3 months

Setting up Xwiki for development

by xwicaforrica＠gmail.com

Greetings! I'm currently working on my master thesis, I've chosen XWiki as the wiki system that will support my platform. I used the Windows Installer in http://www.xwiki.org/xwiki/bin/view/Main/Download and easily set up a local xwiki instance, in order to explore it and learn how it works. But I shall probably have to adapt or create some functionality related to the Audit requirements I have defined (I'll save this for future posts ;) ), so I'd like to set up a development xwiki project using Eclipse. I followed the instructions in http://www.xwiki.org/xwiki/bin/view/Community/BuildingInEclipse: I checked out the source from the trunks-devs, ran mvn eclipse:eclipse and created a new eclipse workspace, which I included in a new variable M2_REPO. Finally I created a java project and did an import from the folder with all the code (xwiki-platform-tools, xwiki-platform-core, xwiki-platform-web, xwiki-platform-plugins and the others). The result was 22070 errors and 390 warnings in the 'Problems' tab! I think I must have missing something related to the building process.. being my first experience with eclipse, besides the tutorials, surely doesn't help! Could you guys help me? Thanks in advance and congratulations for the xwiki platform. I hope I can contribute with some code or plugins :) Best regards, Ricardo Pinto. Ps: By the way, I'm using Windows XP, Eclipse 3.2, JDK 1.5.10, Tortoise SVN (and will use mySQL after setting up the IDE environment).

17 years, 3 months

xwiki database backup

by anujssharma86＠yahoo.co.in

I am working on XWiki MySQL database backup. I have to take the database backup and export it to other system within xwiki, so that the other system will have all the data . Can you please me, is there any plugin available for it or I have to create one new page and do some programming? If yes, then what code I have to write for the same. Thanks, Anuj

17 years, 3 months

← Newer
1
2
3
4
5
6
7
8
9
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs August 2007