Hi Andrea
Hi Stefan,
sorry for the late reply, I had quite a week.
I tracked down the problem and opened a jira issue:
http://jira.codehaus.org/browse/GEOS-3846
In the meantime I’ve committed a temporary workaround in WPS,
you can update and it should be working
No problem. Thanks for opening an jira issue and the workaround. In the meantime I just commented out few lines so I had really quick and dirty workaround for me.
I have to come up with some other question:
I’m following your design guide and the examples from David from last december. Why is a FeatureCollection.class from the input parameters mapped to “text/xml; subtype=wfs-collection/1.0”? I was trying to understand what’s going on in DescribeProcess.java and ComplexPPIO/XMLPPIO/WFSPPIO.java.
regards
Stefan
Ziegler Stefan ha scritto:
Hi Andrea
Hi Stefan,
sorry for the late reply, I had quite a week.
I tracked down the problem and opened a jira issue:
http://jira.codehaus.org/browse/GEOS-3846
In the meantime I've committed a temporary workaround in WPS,
you can update and it should be working
No problem. Thanks for opening an jira issue and the workaround. In the meantime I just commented out few lines so I had really quick and dirty workaround for me.
I have to come up with some other question:
I'm following your design guide and the examples from David from last december. Why is a FeatureCollection.class from the input parameters mapped to "text/xml; subtype=wfs-collection/1.0"? I was trying to understand what's going on in DescribeProcess.java and ComplexPPIO/XMLPPIO/WFSPPIO.java.
To make it explicit we're returning a WFS 1.0 collection and not some
random XML, or a WFS 1.1 collection for that matter.
There is no official xml type for it, the wfs spec just says "text/xml",
but I found it common practice on the net to better qualify a mime type
using an extra qualifier, something like "image/png; mode=24bit".
I did not have time to guess the best way since I'm not getting
any paid time to work on this, so I just used the first thing
that came to mind, "text/xml; subtype=wfs-collection/1.0".
I welcome more standard compliant suggestion.
It has to be something allowing to tell apart WFS 1.0 and WFS 1.1
collections as well as other XML ways to express a feature
collection
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.