[Geoserver-users] DescribeProcess response in Geoserver

Hello,

I am creating my own WPS in GeoServer.
The WPS client, which communicates with GeoServer, needs to know the Schema
and the Encoding parameter for ComplexData.

I know, that these parameters are defined as optional in the WPS
Specification. However, in GeoServer the Response document doesn't contain
these parameters. Also, for a literal input parameter, the parameter
"DataType" isn't shown.

What do I have to change in GeoServer, that these parameters are shown in
the response document? (Respectively, how can I edit the parameters?)

Thanks for helping.

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/DescribeProcess-response-in-Geoserver-tp5046397.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

On Fri, Apr 12, 2013 at 3:23 PM, vermesser123 <maxmeier35@anonymised.com> wrote:

Hello,

I am creating my own WPS in GeoServer.
The WPS client, which communicates with GeoServer, needs to know the Schema
and the Encoding parameter for ComplexData.

I know, that these parameters are defined as optional in the WPS
Specification. However, in GeoServer the Response document doesn't contain
these parameters. Also, for a literal input parameter, the parameter
"DataType" isn't shown.

What do I have to change in GeoServer, that these parameters are shown in
the response document? (Respectively, how can I edit the parameters?)

At the moment, it's simple, you cannot, there is no support for specifying
the schema
for complex data. However, it may not be that hard to change.

GeoServer WPS is based on the GeoTools process API, where a process is meant
to consume and produce java objects, and then there are the
ProcessParameterIO
that can marshall/unmarshall between java objects and external
representations.

So the thing would likely be to modify the XMLPPIO base class to allow the
specification
of schemas, modify the subclasses to report a schema, and have
DescribeProcess
leverage that information.

Honestly I never found the schema reference to be of much value, take the
case of GML,
say you want to encode a Point, if you point to the GML schema you don't
specify
much of anything, if you create a custom schema only having Point you have
to
import the GML schemas anyways, and it's ridiculous that you have to
replicate portions
of a standard schema to start with.
The right thing to do imho would be to be able to specify both a schema and
a qualified
name of the element inside the schema that you're producing, but that's not
possible
as far as I know.

Cheers
Andrea

--

GeoServer training in Milan, 6th & 7th June 2013! Visit
http://geoserver.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------