From: Ben Caradoc-Davies (JIRA) <jira@co...> - 2010-01-27 06:31:02
app-schema DataAccess producing "null" prefix for secondary namespaces
Issue Type: Bug
Components: data app-schema
Reporter: Ben Caradoc-Davies
Assignee: Ben Caradoc-Davies
[email addresses removed: see geoserver-users list for addresses]
-------- Original Message --------
Subject: [Geoserver-users] App-schema DataAccess producing "null" prefix for secondary namespaces
Date: Wed, 20 Jan 2010 08:55:22 +0800
From: Dustin Parker
I have an app-schema DataAccess and a target schema that spans several
namespaces. A GetFeature request on my complex feature type uses the
right prefix for the namespace used by the feature type and the
workspace it's in, but it actually prints the literal string "null" as
the prefix for other namespaces. (I guess I just expected it to produce
something like "ns1", "ns2" for unbound namespaces.)
I see that the WFS response object is getting a WFSConfiguration object
that has an XMLSchema with some namespace-prefix mappings. Those
mappings are used as the declared namespaces of the output XML document.
The source of /those/ mappings seems to be
method queries the catalog for all FeatureTypeInfo metadata and adds
their namespace info into the schema.
It seems that if I want to get my extra namespaces into Geoserver, I
need to declare a FeatureType that I don't really want. I tried placing
another namespace.xml file in my workspace directory (namespace2.xml)
and creating a new FeatureType in that workspace that references the new
namespace by id. In the debugger, however, it seems that the new
FeatureType references the "default" namespace, even though the new
namespace is in the catalog. (Aside: I just used the debugger in
#addApplicationTypes to fake the right namespace and prefix and the
document encoded correctly, so it seems like this /will/ work if I can
get the FeatureType to have the right namespace.)
So, I guess my questions are:
1. How do I get additional prefix-namespace bindings in my output XML?
1.1. Is there a nice way to get MappingDataAccess to do it?
1.2. If I have to declare new FeatureTypes, what's the least painful
method of creating these unwanted FeatureTypes?
2. Are multiple namespaces per workspace really supported?
3. Why did the new FeatureType end up with the default namespace?
Thanks for any help,
Dustin Parker - Forward Slope, Inc.
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira