Hi,
trying to get a capabilities on trunk today I got this
stack trace:

05 giu 15:57:47 ERROR [geoserver.ows] -
java.io.IOException
        at 
org.geoserver.wfs.response.GetCapabilitiesResponse.write(GetCapabilitiesResponse.java:62)
        at org.geoserver.ows.Dispatcher.response(Dispatcher.java:617)
        at 
org.geoserver.ows.Dispatcher.handleRequestInternal(Dispatcher.java:194)
        at
....
....
Caused by: javax.xml.transform.TransformerException: Translator error
        at 
org.geotools.xml.transform.TransformerBase.transform(TransformerBase.java:132)
        at 
org.geotools.xml.transform.TransformerBase.transform(TransformerBase.java:107)
        at 
org.geoserver.wfs.response.GetCapabilitiesResponse.write(GetCapabilitiesResponse.java:60)
        ... 55 more
Caused by: java.lang.IllegalStateException: This featureType is not enabled
        at 
org.vfny.geoserver.global.FeatureTypeInfo.getNameSpace(FeatureTypeInfo.java:675)
        at 
org.geoserver.wfs.CapabilitiesTransformer$WFS1_1$CapabilitiesTranslator1_1.featureType(CapabilitiesTransformer.java:1235)
        at 
org.geoserver.wfs.CapabilitiesTransformer$WFS1_1$CapabilitiesTranslator1_1.featureTypeList(CapabilitiesTransformer.java:1138)
        at 
org.geoserver.wfs.CapabilitiesTransformer$WFS1_1$CapabilitiesTranslator1_1.encode(CapabilitiesTransformer.java:826)
        at 
org.geotools.xml.transform.TransformerBase$XMLReaderSupport.parse(TransformerBase.java:702)
        at 
org.apache.xalan.transformer.TransformerIdentityImpl.transform(TransformerIdentityImpl.java:484)
        at 
org.geotools.xml.transform.TransformerBase$Task.run(TransformerBase.java:295)
        at 
org.geotools.xml.transform.TransformerBase.transform(TransformerBase.java:128)
        ... 57 more


This is happening because the catalog is now returning a non enabled 
feature type. The old catalog did not load the disabled feature types at
all.
The new one does, and it makes some sense, since it has to be both
live catalog and "config", whilst in the old code the non enabled
feature type could be kept seperate in the config objects.

Now, I can add some filtering in Data for the moment to restore the
old behaviour (which is probably needed for coverages as well, did
not check), but in the long run we'll have to change the client
code to account for this.

Opinions on how to proceed?
Cheers
Andrea

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Reply via email to