mind, got the module ready and its a quasi-verbatim copy of the
restconfig-wms one (as so are the wfs and wcs ones), but just realized it
should be a community module first?
On Fri, 8 Nov 2019 at 15:14, Gabriel Roldan
wrote:
> Hi, I need to configure per-workspace OWS services from a downstream
Hi, I need to configure per-workspace OWS services from a downstream
applications. It's all good for WMS, WFS, WCS, but it seems there's
no ServiceSettingsController subclass for WMTS.
Wonder if that's a simple omission and in that case I can supply a patch,
or there's another reason for it. At a
Hi David
Thank You very much.I will have look and test the implementation.
On Thu, Jan 27, 2011 at 6:54 PM, David Winslow wrote:
> There's actually already a Java client for RESTConfig in the community
> modules section of the source repository - so a good first step would be to
> read over tha
There's actually already a Java client for RESTConfig in the community
modules section of the source repository - so a good first step would be to
read over that code and try to use it for a few tasks. If you don't find
any bugs while doing that, perhaps you could start working on a section of
the
HI Devs,
I am interested in the project to implement a RestConfig client for Geo
server using the existing A.Since i am new to Geoserve i started from
building the trunk and following the sample tutorials
to understand the project.I was able to test run with in the IDE and deploy
in tomcat externa
On Fri, Jan 14, 2011 at 12:50 AM, Andrea Aime
wrote:
> On Fri, Jan 14, 2011 at 3:14 AM, Justin Deoliveira
> wrote:
> > Hi all,
> > The restconfig module has been moved to a core module. However when doing
> > the move I found that there is actually a test dependency from restconfig
> on
> > the h
On Fri, Jan 14, 2011 at 3:14 AM, Justin Deoliveira wrote:
> Hi all,
> The restconfig module has been moved to a core module. However when doing
> the move I found that there is actually a test dependency from restconfig on
> the h2 extension. The reason being for some restconfig tests that work
>
Hi all,
The restconfig module has been moved to a core module. However when doing
the move I found that there is actually a test dependency from restconfig on
the h2 extension. The reason being for some restconfig tests that work
against database backends. So long story short without the dependenc
Hi guys,
I've noticed a twitter on the topic today and found this:
http://github.com/tmcw/wfs_geoserver
Never been a PHP guy myself, but it sure looks interesting
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
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-
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
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
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
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
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
Thanks, so the paragraph states:
"The newly created resource can be referenced by the URI(s) returned in
the entity of the response, with the most specific URI for the resource
given by a Location header field. The response SHOULD include an entity
containing a list of resource characteristics
Hi,
On Fri, May 8, 2009 at 5:01 PM, Justin Deoliveira wrote:
> Right, after looking at the commits I noticed this was the case, which is
> sort of a special case.
>
> As per your comment:
>
> >From [1] I see that the response should contain some info
> > about the newly created resource
Right, after looking at the commits I noticed this was the case, which
is sort of a special case.
As per your comment:
>From [1] I see that the response should contain some info
> about the newly created resource.
Where exactly is this. I read the specification of the PUT method and
Hi Justin,
I'm talking about the CoverageStoreFileResource which allows to add a new
coverage using the following syntax with PUT:
/workspaces//coveragestores//file[.]
I have noticed that when done, it returns a STATUS_CREATED in the response.
Daniele
On Fri, May 8, 2009 at 3:55 PM, Justin Deol
hi Daniele,
Where exaclty is a 201 being set as the response code for a PUT. The
semantic we are following for restconfig is to have PUT only be used to
modify existing resources, therefore only returning a 200.
POST being used to create new resources on the other hand does return a
201.. And
I'd say at least the layer name so that I can query it right away.
Simone.
---
Ing. Simone Giannecchini
GeoSolutions S.A.S.
Owner - Software Engineer
Via Carignoni 51
55041 Camaiore (LU)
Italy
phone: +39 0584983027
fax: +39 0584983027
mob:
Hi list,
I'm doing some work on improving restconfig.
When putting some resource via rest in geoserver, in case everything goes
ok, you will receive a response with a return code = 201 --> handlePut does
this: getResponse().setStatus( Status.SUCCESS_CREATED );
>From [1] I see that the response shou
Alessio Fabiani ha scritto:
> Hi guys,
>
> I almost agree with you David, and also I think RESTConfig should not be
> included into 1.7.x release at least in this very incomplete state, but
> anyway it is a valid alternative to interact with GS catalog
> configuration ... so what I'm thinking i
Hi guys,
I almost agree with you David, and also I think RESTConfig should not be
included into 1.7.x release at least in this very incomplete state, but
anyway it is a valid alternative to interact with GS catalog configuration
... so what I'm thinking is that maybe we can distribute it as a GeoS
Wow, a lot to digest ;).
But I think in the end I agree with you. It does not seem to be a huge
win to spend a lot of time getting REST working on 1.7.x if we just have
to redo a lot of it for 2.0 anyways. Especially since its just going to
be something that ties us down as the api will be chan
Hi all,
As I'd like to be able to include RESTConfig in 1.7.0 when it comes out
I am trying to assess its current state and work out how much needs to
happen before it makes sense to consider it for inclusion. Right now it
provides configuration for datastores, coveragestores, featuretypes,
c
Andrea Aime wrote:
> Alessio Fabiani ha scritto:
>> Hi guys,
>>
>> I made few improvements to the GeoServer RESTConfig and sldService
>> stuff which I would like to briefly discuss here, and in case of
>> interest I can commit it:
>>
>> 1. DataStoreFileResource: this class originally was intended
Andrea Aime wrote:
>
> Is it any better than using curl on the command line? (did not look,
> just wondering).
FYI, I have found Poster (a FireFox add-on) to be rather handy for
testing web-services interactively.
https://addons.mozilla.org/en-US/firefox/addon/2691
Luc
Andrea Aime ha scritto:
> POST == creation of new resource. If your code is just returning
> a style without storing it on the server, the request should be a GET.
> Moreover, why specify a datastore? Wouldn't it be better to have
> a GET request on the FeatureType node that looks like
>
> .../to
Alessio Fabiani ha scritto:
> Hi guys,
>
> I made few improvements to the GeoServer RESTConfig and sldService stuff
> which I would like to briefly discuss here, and in case of interest I
> can commit it:
>
> 1. DataStoreFileResource: this class originally was intended to let
> GeoServer get a
Hi guys,
I made few improvements to the GeoServer RESTConfig and sldService stuff
which I would like to briefly discuss here, and in case of interest I can
commit it:
1. DataStoreFileResource: this class originally was intended to let
GeoServer get a shapefile and create a new datastore. I correc
31 matches
Mail list logo
