"SRS List" link in FeatureType Edit form yields 404
---
Key: GEOS-1971
URL: http://jira.codehaus.org/browse/GEOS-1971
Project: GeoServer
Issue Type: Bug
Components: Configuration
Hi Andrea,
I recently ran into some of the same concerns with the new catalog
implementation. As you know there is currently no real DTO layer, which
means that changes made via the UI or wherever else are instantly made
live. Now.. this if course has issues with synchronization, beign able
to
Acegi filter integration is not covering the /ows path
--
Key: GEOS-1970
URL: http://jira.codehaus.org/browse/GEOS-1970
Project: GeoServer
Issue Type: Bug
Affects Versions: 1.6.4
See http://gridlock.openplans.org:8080/hudson/job/geoserver-trunk/230/changes
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourcefor
Hi all,
the implementation of GSIP 19 has just been enabled on trunk.
You can play with it by defining your layers.properties file
as instructed at:
http://geoserver.org/display/GEOS/GSIP+19+-+Per+layer+security
The changes on that file are detected live, so you can change
and instantly see the ef
See http://gridlock.openplans.org:8080/hudson/job/geoserver-trunk/229/changes
Changes:
[aaime] GEOS-1969, enabling secured catalog as default catalog
[aaime] Fixing unwrapping when accessing the catalog
--
[...truncated 197 lines...]
[INFO] Using default
Implement GSIP 19, per layer security subsystem
---
Key: GEOS-1969
URL: http://jira.codehaus.org/browse/GEOS-1969
Project: GeoServer
Issue Type: Improvement
Components: Security
Hi,
in the security implementation work I have to create a ton of wrappers.
These classes are needed in order to make the current user do only
what he's supposed to do, that is, if the current user can only read
a feature type, the wrappers make sure the service really see a read
only object, be i
Hi,
trying to get a capabilities on trunk today I got this
stack trace:
05 giu 15:57:47 ERROR [geoserver.ows] -
java.io.IOException
at
org.geoserver.wfs.response.GetCapabilitiesResponse.write(GetCapabilitiesResponse.java:62)
at org.geoserver.ows.Dispatcher.response(Dispatcher.java
We need to distinguish the 'profile pattern' from the idea of a profile
artefact.
A TimeSeriesObservation is a feature type that restricts an Observation
by specifying the type of the "result" property.
Thus it is a 'profile' (according to ISO 19106 profiles), formalised as
a model (and GML sch
Andrea Aime wrote:
I'm actually a bit skeptical about the idea of having the feature
type and the test parameters being configured independently. Different
feature types will have at least different attributes, so in order
to make up a generic "in between dates" test you'll have to at
least provi
Hi Rob,
so would these "profiles" be in case of AWDIP time and location? Some
featureTypes only implement one of them, like SingleSitePhenomTimeSeries
e.g. time and others like SiteSamplingStatistics both.
There would be separate tests for time and location which could be run
to the correspond
See http://gridlock.openplans.org:8080/hudson/job/geoserver-trunk/226/changes
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourcefor
See http://gridlock.openplans.org:8080/hudson/job/geoserver-trunk/225/changes
Changes:
[aaime] Added read only wrappers tests, reorganized tests a little
--
[...truncated 313 lines...]
[INFO] Compiling 13 source files to
http://gridlock.openplans.org:8080
14 matches
Mail list logo
