[Geoserver-users] schema.xml support in 1.7.2

GeoServer GeoServer User
1

I'm holding off upgrading my 1.6.5 production machine to the latest becuase I
can't get the featuretype schema.xml functionality to work. I've seen some
other posts talking about how the UI to manage the featuretype schemata is
not working, but what about the underlying functionality? I'm happy to edit
schema.xml by hand, but when I do this to my 1.7.2 installation it does not
work (it seems to always pass back all the elements from the underlying
table).

Is this a regression of functionality? Is there some other way to control
what describefeaturetype sends back? (I'm trying to suppress some of the
columns from the source table)

Regards,

Tom

--
View this message in context: http://www.nabble.com/schema.xml-support-in-1.7.2-tp21939818p21939818.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

2

Hi Tom,

Indeed it is a regression... a tough one to fix though. The schema.xml stuff was done sort of poorly and is hard to maintain which is the reason why it has degraded.

1.7.x does have a similar concept but the file is named schema.xsd. It is not related at all to the user interface, only to WFS. And currently it only works for describe feature type. A getfeature will ignore the file.

Getting it to work with getfeature is doable, but not trivial. Can you open an issue in the bug tracker about this.

Apologies for the inconvenience.

-Justin

tlaverty wrote:

I'm holding off upgrading my 1.6.5 production machine to the latest becuase I
can't get the featuretype schema.xml functionality to work. I've seen some
other posts talking about how the UI to manage the featuretype schemata is
not working, but what about the underlying functionality? I'm happy to edit
schema.xml by hand, but when I do this to my 1.7.2 installation it does not
work (it seems to always pass back all the elements from the underlying
table).

Is this a regression of functionality? Is there some other way to control
what describefeaturetype sends back? (I'm trying to suppress some of the
columns from the source table)

Regards,

Tom

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

3

This is important to know. I have several layers that I was using
schema.xml to "hide" certain fields.
I also just confirmed that with 1.7.2 on my PC my schema.xml is not read
for DescribeFeatureType or GetFeature.

For my case since it's only half a dozen layers or so are affected I'll
just create views with the subset of fields and reload these into
GeoServer. I kind of liked the schema.xml system though, it seemed
elegant and made less work massaging the data. But I can live without
it.

Note the 1.7.2 UI still offers the ability to create this schema.xml,
but it produces the error talked about here:
https://fisheye.codehaus.org/browse/GEOS-2555

4

Good to know Aleda. Two users speaking up about a regression is good enough for me. I am however reluctant to fix UI part since it never really worked properly. Would that be a show stopper for anyone?

Freeman, Aleda (EEA) wrote:

This is important to know. I have several layers that I was using
schema.xml to "hide" certain fields.
I also just confirmed that with 1.7.2 on my PC my schema.xml is not read
for DescribeFeatureType or GetFeature.

For my case since it's only half a dozen layers or so are affected I'll
just create views with the subset of fields and reload these into
GeoServer. I kind of liked the schema.xml system though, it seemed
elegant and made less work massaging the data. But I can live without
it.

Note the 1.7.2 UI still offers the ability to create this schema.xml,
but it produces the error talked about here:
https://fisheye.codehaus.org/browse/GEOS-2555

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

5

No, not having a working UI is not a show-stopper. I'd be very pleased
to have the schema.xml/xsd functionality back for getFeature requests in
any form (db views won't work in my situation...)

Thanks for looking into this,

Tom

-----Original Message-----
From: Justin Deoliveira [mailto:jdeolive@anonymised.com]
Sent: Wednesday, February 11, 2009 11:54 AM
To: Freeman, Aleda (EEA)
Cc: Tom Laverty; geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] schema.xml support in 1.7.2

Good to know Aleda. Two users speaking up about a regression is good
enough for me. I am however reluctant to fix UI part since it never
really worked properly. Would that be a show stopper for anyone?

Freeman, Aleda (EEA) wrote:

This is important to know. I have several layers that I was using
schema.xml to "hide" certain fields.
I also just confirmed that with 1.7.2 on my PC my schema.xml is not

read

for DescribeFeatureType or GetFeature.

For my case since it's only half a dozen layers or so are affected

I'll

just create views with the subset of fields and reload these into
GeoServer. I kind of liked the schema.xml system though, it seemed
elegant and made less work massaging the data. But I can live without
it.

Note the 1.7.2 UI still offers the ability to create this schema.xml,
but it produces the error talked about here:
https://fisheye.codehaus.org/browse/GEOS-2555

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

6

Yup, I can do without the UI.

7

Ok, I have created a jira issue for this and scheduled for 1.7.3

http://jira.codehaus.org/browse/GEOS-2619

-Justin

Freeman, Aleda (EEA) wrote:

Yup, I can do without the UI.

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.