[Geoserver-users] xlink:ref not well encoded in WFS response (app schema)

GeoServer GeoServer User
1

Hi,

I’ve defined a complex feature mapping file, with some ReferencedType inside.

Mapping file :

xlink [http://www.w3.org/1999/xlink](http://www.w3.org/1999/xlink) xlink:href if_then_else(isNull(boundary), Expression.NIL, strConcat('urn:x-inspire:specification:gmlas:AdministrativeUnit:3.0:', boundary))

This gives as response
<au:boundary href=“urn:x-inspire:specification:gmlas:AdministrativeUnit:3.0:8269”/>

The problem is that href is encoded but not xlink:href !
And in the top element of the xml response, the namespace is not declared ! (should have xmlns:xlink=“http://www.w3.org/1999/xlink”)

I’m using master branch of geotools and geoserver…

Do you know where to look in order to make xlink encoding working properly ?

Ty

–
Florent Gravin
CampToCamp - Chambéry
0479444492

2

I’ve found that xlink:href is well encoded if you use WFS 1.1.0 and not if you use 2.0.0 (encode href instead).
Still wondering why

On Mon, Sep 17, 2012 at 11:46 AM, Florent Gravin <florent.gravin@anonymised.com> wrote:

Hi,

I’ve defined a complex feature mapping file, with some ReferencedType inside.

Mapping file :

xlink [http://www.w3.org/1999/xlink](http://www.w3.org/1999/xlink) xlink:href if_then_else(isNull(boundary), Expression.NIL, strConcat('urn:x-inspire:specification:gmlas:AdministrativeUnit:3.0:', boundary))

This gives as response
<au:boundary href=“urn:x-inspire:specification:gmlas:AdministrativeUnit:3.0:8269”/>

The problem is that href is encoded but not xlink:href !
And in the top element of the xml response, the namespace is not declared ! (should have xmlns:xlink=“http://www.w3.org/1999/xlink”)

I’m using master branch of geotools and geoserver…

Do you know where to look in order to make xlink encoding working properly ?

Ty

–
Florent Gravin
CampToCamp - Chambéry
0479444492

–
Florent Gravin
CampToCamp - Chambéry
0479444492

3

Hi Florent,

App-schema doesn't support WFS 2.0.0, however you can use WFS 1.1.0 with GML
3.2 by specifying outputFormat=gml32 and version=1.1.0.
With gml 3.2, you need to specify secondary namespaces in a separate
namespace.xml and workspace.xml as shown in
http://docs.geoserver.org/stable/en/user/data/app-schema/supported-gml-versions.html#secondary-namespace-for-gml-3-2-1-required.
Try specifying namespace.xml and workspace.xml for xlink.
I hope that helps.

Cheers
Rini

--
View this message in context: http://osgeo-org.1560.n6.nabble.com/xlink-ref-not-well-encoded-in-WFS-response-app-schema-tp5002307p5004518.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

4

I noticed a similar problem with WFS version 2.0.0. I'm using app-schema
configuration and get schema resolution with the following WFS GetFeature
request GetFeature-AppSchema.xml
<http://osgeo-org.1560.x6.nabble.com/file/n5060964/GetFeature-AppSchema.xml&gt;
:

http://localhost:8080/geoserver/wfs?service=wfs&version=1.1.0&request=GetFeature&typeName=HeatFlow:HeatFlow

But when I try the version 2 request:

http://localhost:8080/geoserver/wfs?service=wfs&version=2.0.0&request=GetFeature&typeName=HeatFlow:HeatFlow&maxFeatures=10

I get the error: "The prefix &quot;null&quot; for element
&quot;null:Envelope&quot; is not bound."

Is there a time frame for a fix, where the WFS version 2.0.0 will work with
app-schemas?

Thanks,
Christy

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/xlink-ref-not-well-encoded-in-WFS-response-app-schema-tp5002307p5060964.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

5

Hi Christy,

I raised a JIRA issue here: https://jira.codehaus.org/browse/GEOT-4894
I will try my best to have a look this month, and see if the issue is
related with xlink.

Cheers
Rini

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/xlink-ref-not-well-encoded-in-WFS-response-app-schema-tp5002307p5161027.html
Sent from the GeoServer - User mailing list archive at Nabble.com.