[Geoserver-users] WPS Chaining problems with GeoServer 2.1.3 and 2.1.4

[Peter Hopfgartner]

Hi list

I doing some work with WPS on GeoServer. As by now, I was not able to 
chain processes on GeoServer 2.1.3 and 2.1.4, getting messages, like the 
following:

<ows:ExceptionText>Process failed during execution
Process execution 2d7b1ee3-1a96-4158-a75b-cddef34ddb7a failed
Failed to retrieve value for input features
null</ows:ExceptionText>

What I am trying to accomplish here is to reproject the buffer of 
linestrings data:

<?xml version="1.0" encoding="UTF-8"?>
<wps:Execute version="1.0.0" service="WPS" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns="http://www.opengis.net/wps/1.0.0"; 
xmlns:wfs="http://www.opengis.net/wfs"; 
xmlns:wps="http://www.opengis.net/wps/1.0.0"; 
xmlns:ows="http://www.opengis.net/ows/1.1"; 
xmlns:gml="http://www.opengis.net/gml"; 
xmlns:ogc="http://www.opengis.net/ogc"; 
xmlns:wcs="http://www.opengis.net/wcs/1.1.1"; 
xmlns:xlink="http://www.w3.org/1999/xlink"; 
xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 
http://schemas.opengis.net/wps/1.0.0/wpsAll.xsd";>
   <ows:Identifier>gs:Reproject</ows:Identifier>
   <wps:DataInputs>
     <wps:Input>
       <ows:Identifier>features</ows:Identifier>
       <wps:Reference mimeType="text/xml; subtype=wfs-collection/1.0" 
xlink:href="http://geoserver/wps"; method="POST">
         <wps:Body>
           <wps:Execute version="1.0.0" service="WPS">
<ows:Identifier>gs:BufferFeatureCollection</ows:Identifier>
             <wps:DataInputs>
               <wps:Input>
                 <ows:Identifier>feature collection</ows:Identifier>
                 <wps:Reference mimeType="text/xml; 
subtype=wfs-collection/1.0" xlink:href="http://geoserver/wfs"; method="POST">
                   <wps:Body>
                     <wfs:GetFeature service="WFS" version="1.0.0" 
outputFormat="GML2">
                       <wfs:Query typeName="apbz:wege_meran"/>
                     </wfs:GetFeature>
                   </wps:Body>
                 </wps:Reference>
               </wps:Input>
               <wps:Input>
                 <ows:Identifier>width of the buffer</ows:Identifier>
                 <wps:Data>
                   <wps:LiteralData>5</wps:LiteralData>
                 </wps:Data>
               </wps:Input>
             </wps:DataInputs>
             <wps:ResponseForm>
               <wps:RawDataOutput mimeType="text/xml; 
subtype=wfs-collection/1.0">
                 <ows:Identifier>result</ows:Identifier>
               </wps:RawDataOutput>
             </wps:ResponseForm>
           </wps:Execute>
         </wps:Body>
       </wps:Reference>
     </wps:Input>
     <wps:Input>
       <ows:Identifier>forcedCRS</ows:Identifier>
       <wps:Data>
         <wps:LiteralData>EPSG:25832</wps:LiteralData>
       </wps:Data>
     </wps:Input>
     <wps:Input>
       <ows:Identifier>targetCRS</ows:Identifier>
       <wps:Data>
         <wps:LiteralData>EPSG:4326</wps:LiteralData>
       </wps:Data>
     </wps:Input>
   </wps:DataInputs>
   <wps:ResponseForm>
     <wps:RawDataOutput mimeType="text/xml; subtype=wfs-collection/1.0">
       <ows:Identifier>result</ows:Identifier>
     </wps:RawDataOutput>
   </wps:ResponseForm>
</wps:Execute>

The request was generated with the WPS builder.
Using GeoServer 2.2RC2, the same WPS request runs fine. So my question: 
should I forget about chaining in 2.1.x or is there some obvious thing 
I'm screwing up?

Regards,

Peter



------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users