What's all the Jetty stuff (seems like alot of stuff ...), but just
curious.
'All' this jetty stuff is actually far smaller (less than half the size)
than what it's replacing, the
good old embedded tomcat. And it's a good bit faster as well. It's a
servlet container and http server, but one that was specifically built
for
being small and easy to embed. I'm _really_ impressed by it, and it
should
allow us to make install and run geoservers that are easily under 10
megs.
The linux one will be as easy as a nice shell script. I'd like a
windows
one, ideally with an install shield and a little java swing start/stop
application like the windows resin.
You can try it out with the 'ant test' and 'ant run' targets (test
builds the source again, run doesn't), and indeed I'd appreciate if
others tested it out to make sure it works.
The only difficulty I've had so far is I can't figure how to get the
changes from the web ui to persist, since it works with the war in a
temp directory.
But that's also got me thinking that it may be a bit weird for us to
write our persistance directly inside the webapp. I mean, people and
the applications themselves move that stuff around and delete it. My
current idea is to create a .geoserver directory in the user's home.
Maven does the same, so I figure it must not be too hard to do in java.
We would store the services.xml and catalog.xml files there. This
would make a nice entry point for users to edit their own config files
(since looking in WEB-INF is a bit weird, and confused when building
from source, and it's in the conf directory). This would have a nice
side effect for developers, as building from source would not wipe out
the changes you made in the web admin tool (which happens now because
it just uses your conf directory). This would make our nice cite
builds not work so well, though I'm sure we could figure out a good
solution. I suppose this begs the question of where you put say the
shapefiles, as maybe files could be in .geoserver/data ? But yeah,
what do people think?
Chris
----------------------------------------------------------
This mail sent through IMP: https://webmail.limegroup.com/