[udig-devel] Server-side uDig

[Aleksander Bandelj]

AFAICT, RSP is intended as complete server-side eclipse workbench with 
AJAX interface. This is obvioulsy a very ambitious undertaking, which 
might take years to complete.

However, migrating geoserver to OSGI bundles or incorporating OSGI 
bundles/services inside it can be done incrementaly. You could start 
with OSGI HttpService, which is also the base for RSP. OSGI bundles can 
then be run standalone, in web application through HttpService servlet 
bridge or possibly through Spring (some form of OSGI runtime wrapping 
bean).

Since HttpService is just servlets and resources, basically, further 
extension points for servlet filters, tag libraries etc. are needed. We 
currently use homebrewn web application extension point, where you 
register web.xml for base web application context. Additional servlets 
and resources are then added through HttpService extension points. Not 
the best or most modular solution, but it works.

OSGI integration in Spring sandbox is also worth looking at. It exports 
Spring context beans as declarative OSGi services. In essence, this adds 
J2EE integration, declarative configuration and other Spring goodies to 
OSGI side and modularisation, dynamic service discovery, wiring and 
management (through JMX) to Spring side.

Chris Holmes wrote:
> It'd be nice to coordinate with GeoServer, since it's sort of the 
> server side equivalent of uDig right now.  We looked at the RSP stuff 
> last week, and have evaluated osgis in the past for use for plugins.  
> See http://docs.codehaus.org/display/GEOS/OSGi.
>
> It wasn't quite mature enough at the time, and I would posit that it's 
> still not quite mature enough for us to shift geoserver architecture 
> to it without some pain.  But it looks like the RSP is considering 
> spring integration, which is what we chose to base our new 
> architecture on. And indeed it's got a lot of wicket in there, which 
> we're very interested in for the UI side, pluggable gui components.
>
> But yeah, exciting work, we'll be very interested on the geoserver 
> side of the fence with what you find.  It'd be great if we could more 
> easily share code between udig and geoserver.
>
> best regards,
>
> Chris
>
> Chris Holmes wrote:
>