We've had similar problems-- you can solve them in a number of different ways
depending on whether and how you can alter the offending servlet and the
configuration of Tomcat andGeoServer. You can put Saxon in a common library
directory, or put Saxon into GeoServer's libraries, or rewrite the
What do you mean by editing layer from WFS service locally? You mean using a
client on the same machine as the server? Are you getting normal results from
WMS and plain WFS when you use other machines?
When you use WFS-T are you getting a error, or nothing?
If an error, do you have a
First, start here:
http://docs.geoserver.org/stable/en/user/production/index.html
I would emphasize:
If you are serving large amounts of rendered imagery, caching is your friend.
GeoWebcache is ready to go for the purpose and integrates well with GeoServer.
If you are serving many features,
That's a very good point that I elided.
We have been thinking to use a more traditional caching method (e.g. mod_cache)
for some of these service operations, but the structure of OGC service calls
makes that difficult.
---
A. Soroka
Digital Research and Scholarship R D and Online Library
The simple answer is yes.
The real answer is: that's going to depend entirely on your mapping client.
It's not at all a GeoServer question. Assuming that you are working to the Web
and that you're using OpenLayers (the Javascript toolkit responsible for the
simple layer previews in GeoServer)
I welcome correction, but my understanding is that since a container runs
inside a JVM, and system properties are set at the level of a JVM, you can't do
that.
Perhaps there's a different parameterization (using something other than a
system property) that could provide the behavior you seek?
