When we request a feature having a "name" attribute, the namespace before the
name attribute is different if the response is in GML2 or GML3:
For GML2, I get
<gb:name>Springdale</gb:name>
For GML3, I get
<gml:name>Springdale</gml:name>
You can also see it here
http://geocon.sunertek.com:8080/geoserver/wfs?request=GetFeature&version=1.0.0&service=WFS&MAXFEATURES=1&typename=AdministrativeArea
vs
http://geocon.sunertek.com:8080/geoserver/wfs?request=GetFeature&version=1.1.0&service=WFS&MAXFEATURES=1&typename=AdministrativeArea
Is this a bug, and if so, is a quick patch doable, or is there a way around
it? And what about beta3, is there a chance that it is fixed in this
release? (Just renaming the atribute to seomething else is not quite simple
in our context)
--
View this message in context: http://www.nabble.com/Bug-with-Feature-having-a-"name"-attribute--(geoserver-1.6-beta2)-tf4480857.html#a12776894
Sent from the GeoServer - User mailing list archive at Nabble.com.
Hi,
Yes this is a known issue. The fix is not so easy because both can be
considered correct. However they should at least be consistent.
In your case which do you prefer. The gml namespace or your app schema
namespace?
boblebel wrote:
When we request a feature having a "name" attribute, the namespace before the
name attribute is different if the response is in GML2 or GML3:
For GML2, I get
<gb:name>Springdale</gb:name>
For GML3, I get
<gml:name>Springdale</gml:name>
You can also see it here
http://geocon.sunertek.com:8080/geoserver/wfs?request=GetFeature&version=1.0.0&service=WFS&MAXFEATURES=1&typename=AdministrativeArea
vs
http://geocon.sunertek.com:8080/geoserver/wfs?request=GetFeature&version=1.1.0&service=WFS&MAXFEATURES=1&typename=AdministrativeArea
Is this a bug, and if so, is a quick patch doable, or is there a way around
it? And what about beta3, is there a chance that it is fixed in this
release? (Just renaming the atribute to seomething else is not quite simple
in our context)
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org
These guys are involved in the same project I am Justin. We want it to use the application namespace, not the gml one.
Did you ever get a chance to look more into my problem, which I suspect is somewhat related to this one, of not returning a geometry in the "location" property (only broken in gml3)? The Sunertek guys are having the same problem. I wasn't able to fix it by renaming the property to "loc", (it then threw an exception instead). Have you guys at Sunertek been able to fix this issue? I'd love to hear about it either way.
Thanks,
Chris
Justin Deoliveira wrote:
Hi,
Yes this is a known issue. The fix is not so easy because both can be
considered correct. However they should at least be consistent.
In your case which do you prefer. The gml namespace or your app schema
namespace?
boblebel wrote:
When we request a feature having a "name" attribute, the namespace before the
name attribute is different if the response is in GML2 or GML3:
For GML2, I get <gb:name>Springdale</gb:name>
For GML3, I get
<gml:name>Springdale</gml:name>
You can also see it here
http://geocon.sunertek.com:8080/geoserver/wfs?request=GetFeature&version=1.0.0&service=WFS&MAXFEATURES=1&typename=AdministrativeArea
vs
http://geocon.sunertek.com:8080/geoserver/wfs?request=GetFeature&version=1.1.0&service=WFS&MAXFEATURES=1&typename=AdministrativeArea
Is this a bug, and if so, is a quick patch doable, or is there a way around
it? And what about beta3, is there a chance that it is fixed in this
release? (Just renaming the atribute to seomething else is not quite simple
in our context)
Chris,
We still have the problem with the "location" property, even after downgrading from jdk1.6 to 1.5...
These guys are involved in the same project I am Justin. We want it to use the application namespace, not the gml one.
Did you ever get a chance to look more into my problem, which I suspect is somewhat related to this one, of not returning a geometry in the "location" property (only broken in gml3)? The Sunertek guys are having the same problem. I wasn't able to fix it by renaming the property to "loc", (it then threw an exception instead). Have you guys at Sunertek been able to fix this issue? I'd love to hear about it either way.
Thanks,
Chris
Justin Deoliveira wrote:
Hi,
Yes this is a known issue. The fix is not so easy because both can be
considered correct. However they should at least be consistent.
In your case which do you prefer. The gml namespace or your app schema
namespace?
boblebel wrote:
When we request a feature having a "name" attribute, the namespace before the
name attribute is different if the response is in GML2 or GML3:
For GML2, I get <gb:name>Springdale</gb:name>
For GML3, I get
<gml:name>Springdale</gml:name>
You can also see it here
http://geocon.sunertek.com:8080/geoserver/wfs?request=GetFeature&version=1.0.0&service=WFS&MAXFEATURES=1&typename=AdministrativeArea
vs
http://geocon.sunertek.com:8080/geoserver/wfs?request=GetFeature&version=1.1.0&service=WFS&MAXFEATURES=1&typename=AdministrativeArea
Is this a bug, and if so, is a quick patch doable, or is there a way around
it? And what about beta3, is there a chance that it is fixed in this
release? (Just renaming the atribute to seomething else is not quite simple
in our context)