Have to be pretty careful rest config doesnt open SQL injection attack paths of course :-)
On Wed, May 5, 2010 at 2:50 AM, <christian.muel...@nvoe.at> wrote: > +1, full agreement > > > Quoting Andrea Aime <aa...@opengeo.org>: > >> christian.muel...@nvoe.at ha scritto: >>> I think we should consider 2 additional facts. >>> >>> 1) The configuration should be usable with geotools alone. >>> 2) Configuring Geoserver using the rest API is a nice thing. >>> >>> IMHO, I would propose an XML config file for geotools instead of a >>> property file. Perhaps we could use a naming convention to avoid a >>> new parameter. >> >> No xml file, no property file. No file at all please. >> From GeoTools you can call JDBCDataStore.addVirtualTable(...) >> and that's it. >> >>> The xml config would also work nice with the rest architecture. >>> >>> Concerning the work flow, I have no preference, since I am doing >>> all geoserver configuration stuff with rest. >> >> What I have proposed in that thread should work then, we can use >> the feature type user map to store the virtual table definition. >> And well, if we want, we can store there a VirtualTable object, >> and roll a xstream custom persister to get a nice xml out of that >> >> Cheers >> Andrea >> >> -- >> Andrea Aime >> OpenGeo - http://opengeo.org >> Expert service straight from the developers. > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Geoserver-devel mailing list > Geoserver-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > ------------------------------------------------------------------------------ _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
