Thanks for replay.

geowolf wrote
> 
> Not sure, it may be that the wfs schema locks prevent wfs feature
> collection parsing
> and generation at the same time (just a guess, could be wrong here).
> 

Could you explain it more fully? Why does processing freeze? No exception is
thrown.


geowolf wrote
> 
> If you need to pull data from inside GeoServer it's much better to use the
> xlink:href="http://geoserver/wfs"; url, which is a fake one GeoServer
> will recognize
> and will make it so that the data is fed into the process directly
> from the source,
> without going through parsing and encoding of the GML
> 

<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="emuia_rysy:EMT_ULICA"/>
    </wfs:GetFeature>
 </wps:Body>
</wps:Reference>

Is this ok?




--
View this message in context: 
http://osgeo-org.1560.n6.nabble.com/WFS-reference-in-WPS-request-tp4359578p4361600.html
Sent from the GeoServer - User mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to