Thank's Andrea; so we can say that the current WPS implementation does not support storing and status, that are not mandatory according to the standarda, but reccomended when managing big datasets. I'm I wrong? We are actually able right now to store a zip file and retrive just the url to the client (as literal data in the output stream of the servlet, I mean...); to accomplish to the Ogc Standard, we should retrive an xml whith the url embedded inside a <ows:Identifier>result</ows:Identifier>; e.g.
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <wps:Execute service="WPS" version="1.0.0" xmlns:wps=" http://www.opengis.net/wps/1.0.0"; xmlns:ows="http://www.opengis.net/ows/1.1"; xmlns:ogc="http://www.opengis.net/ogc"; xmlns:xlink=" http://www.w3.org/1999/xlink"; xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation=" http://www.opengis.net/wps/1.0.0 http://schemas.opengis.net/wps/1.0.0/wpsExecute_request.xsd";> <ows:Identifier>org.n52.wps.server.algorithm.SimpleBufferAlgorithm</ows:Identifier> <wps:DataInputs> <wps:Input> <ows:Identifier>data</ows:Identifier> <wps:Reference schema=" http://schemas.opengis.net/gml/3.1.1/base/feature.xsd"; xlink:href=" http://giv-wps.uni-muenster.de:8080/geoserver/wfs?SERVICE=WFS&VERSION=1.0.0&REQUEST=GetFeature&TYPENAME=ns1:tasmania_roads&SRS=EPSG:4326&OUTPUTFORMAT=GML3"; method="GET"/> </wps:Input> <wps:Input> <ows:Identifier>width</ows:Identifier> <wps:Data> <wps:LiteralData dataType="xs:double">0.05</wps:LiteralData> </wps:Data> </wps:Input> </wps:DataInputs> <wps:ResponseForm> <wps:ResponseDocument storeExecuteResponse="false" lineage="false" status="false"> <wps:Output asReference="true" schema=" http://schemas.opengis.net/gml/3.1.1/base/feature.xsd"; mimeType="text/xml" encoding="UTF-8"> <ows:Identifier>result</ows:Identifier> <ows:Title>result</ows:Title> <ows:Abstract>result</ows:Abstract> </wps:Output> </wps:ResponseDocument> </wps:ResponseForm> </wps:Execute> So to move to the statusSupported I see two new features: 1) add storeSupported= true to the DescribeProcess mechanism 2) retrive the xml response with the url inside. Am I on the right way? On Sat, Oct 29, 2011 at 10:46 AM, Andrea Aime <[email protected]>wrote: > On Sat, Oct 29, 2011 at 10:33 AM, Andrea Aime > <[email protected]> wrote: > > On Sat, Oct 29, 2011 at 8:59 AM, Gianni Barrotta > > <[email protected]> wrote: > >> Hi, > >> I need to set storeSupported=true in the DescribeProcess xml response. > >> > >> <wps:ProcessDescriptions xml:lang="en" service="WPS" version="1.0.0" > >> xsi:schemaLocation="http://www.opengis.net/wps/1.0.0 > >> http://schemas.opengis.net/wps/1.0.0/wpsAll.xsd";> > <ProcessDescription > >> wps:processVersion="1.0.0" statusSupported="false" > storeSupported="false"> > >> <ows:Identifier>gs:TranscodeRaster</ows:Identifier> > >> <ows:Title/><ows:Abstract/> > >> <DataInputs> > >> ---------------- > >> ---------------- > >> > >> With the @DescribeProcess tag in the java class implementing the process > you > >> can set the Identifier, Title and other useful xml elements, but I > couldn't > >> find any way to set the storeSupported attribute. > >> > >> Any idea? > > > > In the current framework store support is not part of the process > > responsibilites, > > it's part of the WPS container responsibilities. > > GeoServer WPS supports store on all requests, just fails to advertise it: > > http://jira.codehaus.org/browse/GEOS-4832 > > Hmm... nope, I was wrong, in fact we have no support for store=true, so the > current behavior is correct, we don't advertise it because it's not there. > > Cheers > Andrea > > > -- > ------------------------------------------------------- > Ing. Andrea Aime > GeoSolutions S.A.S. > Tech lead > > Via Poggio alle Viti 1187 > 55054 Massarosa (LU) > Italy > > phone: +39 0584 962313 > fax: +39 0584 962313 > > http://www.geo-solutions.it > http://geo-solutions.blogspot.com/ > http://www.youtube.com/user/GeoSolutionsIT > http://www.linkedin.com/in/andreaaime > http://twitter.com/geowolf > > ------------------------------------------------------- >
------------------------------------------------------------------------------ Get your Android app more play: Bring it to the BlackBerry PlayBook in minutes. BlackBerry App World™ now supports Android™ Apps for the BlackBerry® PlayBook™. Discover just how easy and simple it is! http://p.sf.net/sfu/android-dev2dev
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
