Vincent,
that would be a good idea to my taste.
HSQLDB doesn't taste serious there for sure.
Our experience with Derby was also pretty good.
This is to compare with MySQL+Apache+(xx-container)+XWiki right?
One angle I found bitten by is that some plugins seem to rely
implicitly MySQL (the activitystream plugin); at least they don't work
with Postgres. I tend to believe that Derby is rather more similar to
Postgres than mysql but that's personal.
Presumably your proposal would make this more tested.
So... you have my +1.
paul
PS: a service, did you say? Does it work well with fonts etc? For some
reasons my xwiki starts on mac always bring up an application icon and
that generally means that the AWT thread is tarted. I always
understood that as bound to FOP... wouldn't that get lost as a service?
On 02-oct.-08, at 23:43, Vincent Massol wrote:
I was wondering today if we could provide a production
quality XE
packaging.
Here's what would be my combo:
* Jetty 6 or 7
* Latest Derby (aka JavaDB - which is included in JDK 1.6 BTW) in
embedded mode
See
http://developers.sun.com/learning/javaoneonline/j1sessn.jsp?sessn=TS-45170…
for performance stats
* Java Service Wrapper
See
http://wrapper.tanukisoftware.org/doc/english/integrate.html
The nice thing with the wrapper is that it can also monitor the JVM
and restart it if hung or not responding, in addition to restarting
the service when the machine is rebooted of course.
I'm confident that we could offer a base packaging that would work
well for relatively large usages of XE and that is still small and
all-
preconfigured.
Basically I think we could replace our current combo of Jetty 5.x +
HSQLDB with this new combo and still get the best of both worlds:
* simple packaging
* production level quality
Whereas our current standalone packaging is not production ready and
is just for getting started with XWiki.
WDYT?
Thanks
-Vincent
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs