Andrea Aime wrote:
>
> My plan was to tackle this by making the UI pluggable, but still pure
> java.
Pure Java... wow ! Do you plan to write your mark-up using servlets ? ;)
> That is, each module has its own configuration UI module, if you
> don't want to use it, don't include its jar and you're done (just like
> you do if you don't want a specific datastore).
As long as there are two packages for every module (the module itself
and the UI), that's perfectly sound. However, there would probably be
some dependencies amongst UI modules (authentication&authorization would
be needed by UI every module, for instance).
Therefore, the GeoServer packaging options may look like this:
1) Development (all-but-the-kitchen-sink).
2) Appliance (just the core functionality, without fancy stuff or the UI).
3) A-la-carte: pick your own modules (possibly using Maven) with or
without the UI.
Regards,
--------------------
Luca Morandini
www.lucamorandini.it
--------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
