Hi Ben and Rini,
Yes, with xlink secondary ns and version1.1.0&outputformat=32 it does work! Many thanks!!!
I discovered the same problem with others e.g. OGC namespaces like om: sam:, and it is despite of the fact that they are in the app-schema-cache directory. I needed to add namespace.xml and workspace.xml to make them work.
Regards,
Valentina
-----Original Message-----
From: Rini.Angreani@anonymised.com [mailto:Rini.Angreani@anonymised.com]
Sent: Wednesday, September 10, 2014 11:36 AM
To: Ben.Caradoc-Davies@anonymised.com; valentina.sagris@anonymised.com
Cc: geoserver-users@lists.sourceforge.net
Subject: RE: [Geoserver-users] App-schema extension: fail to map xlink namespace
Hi Ben, Valentina,
This is a bug indeed. I tried creating secondary namespace for xlink and it doesn't work.
Thanks for reporting. I'll try to fix this before I start my year long leave in 6 weeks time.
https://jira.codehaus.org/browse/GEOT-4894
Cheers
Rini
-----Original Message-----
From: Caradoc-Davies, Ben (Mineral Resources, Kensington)
Sent: Wednesday, 10 September 2014 4:08 PM
To: Valentina Sagris
Cc: geoserver-users@lists.sourceforge.net; Angreani, Rini (Mineral Resources, Kensington)
Subject: Re: [Geoserver-users] App-schema extension: fail to map xlink namespace
Valentina,
this looks like the same problem reported here:
http://osgeo-org.1560.x6.nabble.com/xlink-ref-not-well-encoded-in-WFS-response-app-schema-td5002307.html
Are you using WFS 2.0.0 or WFS 1.1.0 with outputformat=gml32? The latter is reported to work.
Have you tried defining a secondary namespace for xlink?
http://docs.geoserver.org/stable/en/user/data/app-schema/supported-gml-versions.html#secondary-namespace-for-gml-3-2-1-required
I do not think we found out whether this works.
There have been some recent improvements to app-schema support for WFS 2.0.0; it would be good to fix this as well if it is still broken.
Kind regards,
Ben.
On 10/09/14 02:39, Valentina Sagris wrote:
Hi,
have defined xlink in mapping file and in the FT schema
<Namespace>
<prefix>xlink</prefix>
<uri>http://www.w3.org/1999/xlink </uri> </Namespace>
and mapped Client Property
<AttributeMapping>
<targetAttribute>om:observedProperty</targetAttribute>
<ClientProperty>
<name>xlink:href</name>
<value>Concatenate('http://loom-gis.geo.ut.ee/ermas/schemas/sarv/CodeL
ist_ObservablePropertyValue.xml#',
observed_property)</value>
</ClientProperty></AttributeMapping>
but still in the GetFeature resonse I have <om:observedProperty
href="http://loom-gis.geo.ut.ee/ermas/schemas/sarv/CodeList_Observable
PropertyValue.xml#sedimentology_and_lithology"/>
instead of xlink:href
can somebody help?
valentina
--
View this message in context:
http://osgeo-org.1560.x6.nabble.com/App-schema-extension-fail-to-map-x
link-namespace-tp5160960.html Sent from the GeoServer - User mailing
list archive at Nabble.com.
----------------------------------------------------------------------
--------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.
clktrk _______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com> Software Engineer CSIRO Mineral Resources Flagship Australian Resources Research Centre