Re: [Geoserver-devel] restconfig-java

2010-04-13 Thread Justin Deoliveira
Java projects can do that ;) If you could possibly share your scripts or simply document how to make some of the example calls in php that would be much appreciated. Currently (as you have seen) we only have examples in curl: http://docs.geoserver.org/stable/en/user/extensions/rest/rest-config-

Re: [Geoserver-devel] restconfig-java

2010-04-13 Thread Tara Athan
OK, I think I'll go back to my PHP scripts, as the java project has morphed into something way beyond my experience and time available. That should solve my immediate needs and perhaps produce something useful to others as a batch approach to the cURL commands. Thanks for all your insights, Ta

Re: [Geoserver-devel] restconfig-java

2010-04-13 Thread Justin Deoliveira
Hmmm... i would say this is a different issue all together. How to handle changes to the core configuration model (and consequently the representations of resources in the rest api) seems a bit different than having a client being able to round trip all information working against a single vers

Re: [Geoserver-devel] restconfig-java

2010-04-13 Thread David Winslow
Actually, it seems the shared-model-object approach would be subject to the same issues described in this thread, if you mismatched versions of the rest client and the rest service. This would make it tough for distributers of tools based on the RESTConfig service. I guess an easy fix would b

Re: [Geoserver-devel] restconfig-java

2010-04-13 Thread Justin Deoliveira
Hi Tara, First off there was never a schema published for the rest configuration api. The author (Ronak) I believe generated one on his own. There was some discussion on the list about whether to generate a schema or not. But yes your findings sound reasonable and I like the approach (only cha

[Geoserver-devel] restconfig-java

2010-04-12 Thread Tara Athan
I have been looking at the restconfig-java code... I had hoped there would be an easy temporary fix for all the missing parts that would just leave the missing parts unchanged, but the way the code is set up I do not see any easy way to do that. This is because it uses "@Xml..." annotations fro