5 Oct
2008
5 Oct
'08
3:10 a.m.
You can use what we use for Nexus if you're interested. It's a small
wrapper around the Plexus container and we embed Jetty. You can drop
in any WAR file, and it's all enclosed by JSW. We also just did this
for Hudson.
What we are working toward is a way to update the application and then
be able to restart Jetty and the hosted application. We've been using
this setup for about 10 releases of Nexus and it works great.
On 2-Oct-08, at 5:43 PM, Vincent Massol wrote:
Hi,
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
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
To do two things at once is to do neither.
-—Publilius Syrus, Roman slave, first century B.C.