Andrea Aime ha scritto: > Btw, there is a java based rest configuration client in the > trunk community, but in fact it does not use the GS beans, > a new set of beans was created that has JAXP annotations > and Jersey (just yesterday someone on IRC was asking > about Jersey and GS REST and I answered I could not help, > just noticed now that the provided config client is built on it): > > http://svn.codehaus.org/geoserver/trunk/src/community/restconfig-java/src/main/java/org/geoserver/rest/client/datatypes
Sorry I forgot the take home message: they could not use our classes because, I guess, it's not possible to add annotations there. But I don't see anything preventing the usage of our current interfaces and just throwing a runtime exception from the methods that return resources. Though of course not having to do so would be better. The idea of super-interfaces that don't allow access to the resources and the catalog would be a nice fit for this use case. Cheers Andrea PS: a java client could be better off by reusing our implementation as well as the XStream persisters and so on, less risk of getting out of synch with what GS does, but that's another story -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
