27 Jan
2008
27 Jan
'08
11:37 p.m.
Hi Ricardo,
Hi Vincent,
Vincent Massol wrote:
If you develop applications inside the wiki - using scripting and the
xwiki API, as described by those tutorials - you won't experiment API
breakages when upgrading XWiki's version ; and so no reason your apps
stops working. Also, if you start writing Java plugins that uses non-API
internal XWiki classes, then compatibility between versions cannon be
guaranteed (also those breakages has been for now pretty rare, as far as
I've been using XWiki).
Is this correct ?
Jerome.
On Jan 26, 2008, at 5:29 PM, Stefan Rebsamen
wrote:
Very useful links indeed !!
I've kept my hands of using XWiki for applications mainly because I want
to reduce applications maintenance problems caused by changes between
XWiki versions (if there's any) to a minimum .
So, my question are : are there any artifact (class, macro, etc.) that
should be avoided to maximize application compatibility between XWiki
versions ?? for creating such micro application directly in
XWiki. Has anybody
actually made any experiences (good or bad) in implementing them in a
small (50 users) enterprise environment?
Sure we do that all the time.
For a brief introduction you can check for example this article:
http://www.theserverside.com/tt/articles/article.tss?l=XWiki
Or these tutorials:
http://platform.xwiki.org/xwiki/bin/view/DevGuide/Tutorials
Any other considerations to be aware of ??
Thanks ins advance.
--
Víctor A. Rodríguez (http://www.bit-man.com.ar)
El bit Fantasma (Bit-Man) - Algorithm junkie
Perl Mongers Capital Federal (http://cafe.pm.org/)
GNU/Linux User Group - FCEyN - UBA (http://glugcen.dc.uba.ar/)
_______________________________________________
users mailing list
users(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/users