Justin Deoliveira ha scritto:
> Hi all,
> 
> I just added a class called "org.geoserver.config.util.XStreamPersister" 
> which I hope will become the base of taking config objects back to xml 
> land and back. I am hoping it will also be of use to David's REST stuff.
> 
> I have found xstream to be very flexible and straight forward. Tweaking 
> the default settings and adding in some custom stuff I have been able to 
> output xml which looks pretty close to what we actually output today.
> 
> Comments/concerns/feedback welcome.

The code looks nice and clean, the effort to extend it seems low,
it seems possible to achieve extension by adding extensions points
so that other plugins do configure the XStream instance for their
needs. I like it.

Questions:
* how is the final layout of the xml files like?
* is this limited to save just the services for the moment, and in
   particular only wfs?
* what about the catalog?
* why are you not persisting the client properties out of the GeoServer
   object? (xs.omitField(GeoServerInfoImpl.class, "clientProperties");)

Cheers
Andrea


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to