[Geoserver-devel] (GEOS-4943) /geoserver/accessDenied.jsp not found

Brian Youngblood created GEOS-4943:
--------------------------------------

             Summary: /geoserver/accessDenied.jsp not found
                 Key: GEOS-4943
                 URL: https://jira.codehaus.org/browse/GEOS-4943
             Project: GeoServer
          Issue Type: Bug
          Components: Security
    Affects Versions: 2.1.3
            Reporter: Brian Youngblood
            Assignee: Andrea Aime
            Priority: Minor

When a security check fails the server responds with a 404. Log reports missing file.
31 Jan 22:49:30 WARN [servlet.PageNotFound] - No mapping found for HTTP request with URI
[/geoserver/accessDenied.jsp] in DispatcherServlet with name 'dispatcher'

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d

[Geoserver-devel] (GEOS-4944) role disappears from service security rule

Brian Youngblood created GEOS-4944:
--------------------------------------

             Summary: role disappears from service security rule
                 Key: GEOS-4944
                 URL: https://jira.codehaus.org/browse/GEOS-4944
             Project: GeoServer
          Issue Type: Bug
          Components: Security
    Affects Versions: 2.1.3
            Reporter: Brian Youngblood
            Assignee: Andrea Aime
            Priority: Minor

attempting to add a new role from the service security. To recreate..create a service rule wfs.* with a role
called "noaccess" and save. Revisit rule. Role is missing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d

Re: [Geoserver-devel] GeoServer WFS 2.0 limitations

Justin,

the working group is yet to receive all the change requests and has been 
discussing which to discuss [1]. Looks like there are some that are 
similar to your concerns. When I have them, I will compare the change 
requests to GSIP 61 and see if there are any outstanding issues.

Kind regards,
Ben.

[1] "Treebeard: You must understand, young Hobbit, it takes a long time 
to say anything in Old Entish. And we never say anything unless it is 
worth taking a long time to say."
http://www.imdb.com/character/ch0074878/quotes

On 21/01/12 00:23, Justin Deoliveira wrote:
> No I never did... it was something that fell off. Any chance we can just point them at the GSIP? Not sure i have
the time to interact with the working group unfortunately.
>
> On Thu, Jan 19, 2012 at 12:22 AM, Ben
Caradoc-Davies<Ben.Caradoc-Davies@...>  wrote:
> Justin,
>
> did you submit your GSIP 61 findings to the OGC WFS/FES SWG? It has started meeting. The web form is below
(the link provided by Simon). I am sure the group will appreciate your input.
>
> I am an observer on the SWG. I have raised the startIndex issue (clarify zero or one-based index).
>
> Kind regards,
> Ben.

Re: [Geoserver-devel] prefix null with app schema

Alessando,

your mapping file is schema-invalid. targetTypes should contain only one 
FeatureType which can contain multiple schemaUri elements. (At this 
point a nonvalidating parser is used; I'm not sure if it ignores the 
second FeatureType.)

Kind regards,
Ben.

On 31/01/12 22:10, alessandro marrone wrote:
> Hello
>
> I was trying to configure an app-schema to deliver WOML features.
> I’m able to deliver WFS with womlcore and womlswo elements, but when I try to map some GML elements I get
the following  result:
>
> <ows:ExceptionReport version="2.0.0" xsi:schemaLocation="http://www.opengis.net/ows/1.1 http://localhost:8080/geoserver/schemas/ows/1.1.0/owsAll.xsd">
>      <ows:Exception exceptionCode="NoApplicableCode">
>          <ows:ExceptionText>java.io.IOException: The prefix&quot;null&quot; for
element&quot;null:name&quot; is not bound.
> The prefix&quot;null&quot; for element&quot;null:name&quot; is not bound.
> The prefix&quot;null&quot; for element&quot;null:name&quot; is not bound.
>          </ows:ExceptionText>
>      </ows:Exception>
> </ows:ExceptionReport>
>
> I’m using Geoserver 2.2 SNAPSHOT
>
> This is the mapping file:

[Geoserver-devel] (GEOS-4945) Blank Capabilities Responses when ProxyBaseURL is wrong and TILED=true

David Winslow created GEOS-4945:
-----------------------------------

             Summary: Blank Capabilities Responses when ProxyBaseURL is wrong and TILED=true
                 Key: GEOS-4945
                 URL: https://jira.codehaus.org/browse/GEOS-4945
             Project: GeoServer
          Issue Type: Bug
    Affects Versions: 2.1.3
            Reporter: David Winslow
            Assignee: Gabriel Roldán

When the proxy base url setting is wrong, GeoServer responds to WMS GetCapabilities requests with the
TILED=true option with an empty HTTP response, with the mimetype set to a normal OGC XML type instead of an
error.  This can also be demonstrated with a reverse proxy that doesn't adjust the Host: header.

{code}
$ curl
'http://localhost:8000/geoserver/wms?SERVICE=WMS&REQUEST=GetCapabilities&TILED=true&VERSION=1.1.1'
 -v
* About to connect() to localhost port 8000 (#0)
*   Trying 127.0.0.1... connected
* Connected to localhost (127.0.0.1) port 8000 (#0)
> GET /geoserver/wms?SERVICE=WMS&REQUEST=GetCapabilities&TILED=true&VERSION=1.1.1 HTTP/1.1
> User-Agent: curl/7.21.7 (i386-redhat-linux-gnu) libcurl/7.21.7 NSS/3.13.1.0 zlib/1.2.5
libidn/1.22 libssh2/1.2.7
> Host: localhost:8000
> Accept: */*
> 
< HTTP/1.1 200 OK

[Geoserver-devel] Embedded GeoWebCache and upgradability

Hi,
when working with GeoServer configuration we pay special attention to make
sure that it's always possible to upgrade GeoServer from one version to the
next without significant hiccups (not saying that it always works 100%, but at
least we try hard  )

A current thread on the user list seems to imply that the same is not happening
GeoWebCache wise, the schema for geowebcache.xml changed and it seems
that the current code cannot read a document that was working fine with
GeoServer 2.0.2 + embedded GWC, breaking with a schema validation.

How do we handle that so that we're not going to face similar issues in the
future? Maybe change the GWC parsing technology so that it's not
schema dependent, or version the document similarly to OGC specs,
and have a different schema and parser for each version?

Cheers
Andrea

--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead

Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy

phone: +39 0584 962313

[Geoserver-devel] (GEOS-4946) WFS insert transaction returns incorrect feature id

Ray Merkert created GEOS-4946:
---------------------------------

             Summary: WFS insert transaction returns incorrect feature id
                 Key: GEOS-4946
                 URL: https://jira.codehaus.org/browse/GEOS-4946
             Project: GeoServer
          Issue Type: Bug
            Reporter: Ray Merkert
            Assignee: Andrea Aime

I've a got simple setup with a propertyfile store. When I insert a feature into the store, the feature is
properly added, but with an automatically assigned id. It's completely ignoring the id I provide in my request:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><Transaction
xmlns="http://www.opengis.net/wfs" xmlns:ns2="http://www.opengis.net/gml"
xmlns:ns3="http://www.w3.org/1999/xlink" xmlns:ns4="http://www.w3.org/2001/SMIL20/"
xmlns:ns5="http://www.opengis.net/ogc" xmlns:ns6="http://www.opengis.net/ows"
xmlns:ns7="http://dkkn.raytheon.com" xmlns:ns8="http://www.w3.org/2001/SMIL20/Language"
service="WFS" version="1.1.0"><Insert idgen="UseExisting"><ns7:PointFeature
ns2:id="PointFeature.123456789"><ns7:featureName>Boston-WFS</ns7:featureName><ns7:point
ns3:type="simple"><ns2:Point srsName="http://www.opengis.net/gml/srs/epsg.xml#4326"><ns2:coordinates>10,10</ns2:coordinates></ns2:Point></ns7:point></ns7:PointFeature></Insert></Transaction>

Normally, I could deal with this if the response contained the correct feature id: Here is what I get, though:
<?xml version="1.0" encoding="UTF-8"?>
<wfs:TransactionResponse version="1.1.0" xsi:schemaLocation="http://www.opengis.net/wfs
http://localhost:8080/geoserver/schemas/wfs/1.1.0/wfs.xsd"
xmlns:sf="http://www.openplans.org/spearfish" xmlns:ogc="http://www.opengis.net/ogc"
xmlns:gml="http://www.opengis.net/gml"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

Re: [Geoserver-devel] Embedded GeoWebCache and upgradability

On Wed, Feb 1, 2012 at 2:12 PM, Andrea Aime
<andrea.aime <at> geo-solutions.it> wrote:
> Hi,
> when working with GeoServer configuration we pay special attention to make
> sure that it's always possible to upgrade GeoServer from one version to the
> next without significant hiccups (not saying that it always works 100%, but at
> least we try hard  )
>
> A current thread on the user list seems to imply that the same is not happening
> GeoWebCache wise, the schema for geowebcache.xml changed and it seems
> that the current code cannot read a document that was working fine with
> GeoServer 2.0.2 + embedded GWC, breaking with a schema validation.

Schema validation can't break anything because it's not used to
"enforce" the configuration. The validation at start up is _only_ used
to log a warning message. XStream doesn't apply schema validation
afaik.

>
> How do we handle that so that we're not going to face similar issues in the
> future? Maybe change the GWC parsing technology so that it's not
> schema dependent,
As mentioned before, it's not schema dependant. Yet having a schema
and performing the validation at startup is a good way of letting the
user's know if there's something wrong with their config.

>or version the document similarly to OGC specs,
> and have a different schema and parser for each version?

The way it is handled right now is that an xslt stylesheet is applied

[Geoserver-devel] content-type of GetFeature result with resultType=hits

Hey,

Just found out that the response content type of a GetFeature request
with resultType=hits is 'text/xml' instead of 'text/xml;
subtype=gml/xyz'

Is that ok? sorry haven't took the job of looking for the answer in
the spec myself.

Cheers,
Gabriel

--

-- 
Gabriel Roldan
OpenGeo - http://opengeo.org
Expert service straight from the developers.

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] content-type of GetFeature result with resultType=hits

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d

_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@...
https://lists.sourceforge.net/lists/listinfo/geoserver-devel