Hello,
We are using REST to DELETE style information from Geoserver. It works very
well except on one implementation at one of our customers.
A DELETE request returns a 405 error. Normally this would be a MIME-type issue,
but in this case the mime types are just fine.
The setup is: IIS 7,
Hello list,
on our 2.1.3.-geoserver we recently got problems with the layers based on
one specific datastore (which is a directory of spatial files). We didn´t
apply any obvious changes to the layers based on this store (apart from
activating and deactivating a few layers a few weeks ago).
On Thu, Jul 5, 2012 at 11:17 AM, Hugo hfpmart...@gmail.com wrote:
Hello all,
Is it possible to disable publishing capabilities of a geoserver instance?
I mean, disabling all the options of publishing new layers, new styles, and
anything that changes data directory?
My scenario is like the
I have an existing ImagePyramid in GeoServer 2.1.4 (but I can use 2.2 if that
helps).
If it is possible, how can I update the pyramid (add new tiles) without
deleting and re-creating the ImagePyramid store each time?
Regards Casper
FTL is the template language we use to generate HTML output in several
places in GeoServer, including the REST API. If you are seeing FTL errors
in the REST API it is a bug in GeoServer and a JIRA report would be
appreciated.
--
David Winslow
OpenGeo - http://opengeo.org/
On Thu, Jul 5, 2012
Glad to hear it, Michael!
I don't remember needing to set any parameters via Tomcat manager or in any
files ... just directly in my Windows environment variables:
These are the three related to Java or Geoserver that I had set (included
the values just for example). BTW, I didn't see anything
On Thu, Jul 5, 2012 at 4:18 PM, David Winslow dwins...@opengeo.org wrote:
FTL is the template language we use to generate HTML output in several
places in GeoServer, including the REST API. If you are seeing FTL errors
in the REST API it is a bug in GeoServer and a JIRA report would be
Hi Andreas,
I have tried your suggestions and they work fine. However, it is still
possible to make changes via post requests. So my question would be, is it
possible to completely disable these type of things in the slave geoserver
so that, only the master could manage things? I ask this because
Hello
We need to programmatically be able to create layers in geoserver. Based on
the documentation, looks like Geoserver offers rest services to do that. There
are no examples as to how this works in Java. If anybody can provide some
insight into this, that will be great.
Thanks
Ashok
http://code.google.com/p/geoserver-manager/
Regards,
Alessio.
---
Ing. Alessio Fabiani
Founder / CTO GeoSolutions S.A.S.
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: (+39) 0584 96.23.13
fax:
Hello
Trying to install geoserver 2.1.3/2.1.4 on Jboss 5.2 and get the below error.
When I installed Geoserver 2.1.3 on Jboss 4.x version a few months back,
geoserver admin interface worked like a charm. Now I am getting the below
error.
I have tried deleting the following jars from
Can you open a ticket on jira.codehaus.org? If you could also attach the
dataset
and style it would help making sure what you see really gets fixed.
http://jira.codehaus.org/browse/GEOS-5213
I took some time this morning to reproduce the problem on my personal
machine using fresh Geoserver
Was able to solve this problem using the information provided here. However,
still wondering how to utilize the webCache functionality if we have to?
From: Guntu, Ashok (IS) (Contr)
Sent: Thursday, July 05, 2012 11:58 AM
To: geoserver-users@lists.sourceforge.net
Subject: Geoserver 2.1.3 and
On Thu, 5 Jul 2012 10:21:54 PM Casper Børgesen wrote:
I have an existing ImagePyramid in GeoServer 2.1.4 (but I can use 2.2 if
that helps).
If it is possible, how can I update the pyramid (add new tiles) without
deleting and re-creating the ImagePyramid store each time?
I do it by running
On 07/06/2012 12:39 AM, Hugo wrote:
Hi Andreas,
I have tried your suggestions and they work fine. However, it is still
possible to
make changes via post requests.
By post requests you mean the admin ReST interface ?
If so, that can be disabled easily by dropping the relevant JAR.
Regards,
Allesandro,
the mappingName tag was introduced for this use case, to allow
multiply-defined non-feature types to each have a unique internal name
so chaining is unambiguous:
http://docs.geoserver.org/latest/en/user/data/app-schema/feature-chaining.html#multiple-mappings-of-the-same-type
16 matches
Mail list logo