A couple answers inline. On 24/04/2010, at 5:45 AM, Leandro Leal Parente wrote:
> Hi, > > I'm Leandro Leal Parente, 21, from Brazil. I'm on 4th year of Computer > Science on UFG University. Today I work at the Laboratory of image processing > and GIS with computer support and program development. Welcome! > I will develop a web software to processing spatial data with WPS. I will use > one existing WPS implementation (Server and client-side) to realize this > task. Actually, I chose the Geoserver to server and Geotools to client api. > Do Geotools WPS implementation is robust to use on my web software ? When the > module will be stable ? It is not currently funded; as far as I can see no developers are seeking funding to work on it. It is however open to volunteers - would you like to submit patches and gradually take part in its development? I personally expect to work on it in May; but I have no intension of making it generally useful - instead I will be focused on connecting to a few specific WPS services and expect to perform some QA on the way. > Yesterday, I tested the Geotools WPS implementation. I started a Geoserver > with WPS service and I did some request by browser, everything works fine. So > I checkout the last code of geotools svn (http://svn.osgeo.org/geotools/, > Revision 35277) and compile it with maven. I implemented a simple class to > connect to the Geoserver like was describing on WPS Plugin geotools user > guide. I got two problem: > First problem: > When I was sending a describeProcess request, I got this exception: > > java.io.IOException: Server returned HTTP response code: 503 for URL: > http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd > After it I did a sucess request to geoserver, but it is a temporary solution. > I think the right solution is alter the code and put the w3 files on the > gt-xml module jar. That makes sense; difficulty for me is if the standards change over time. But yes - why not submit a patch to include that file; or update the docs so those writing an application can include that file and teach the parser about its location. > Second Problem: > > here is my request code: > > wps = new WebProcessingService(new > URL("http://localhost:8080/geoserver/ows?service=WPS";)); > > DescribeProcessRequest descRequest = wps.createDescribeProcessRequest(); > descRequest.setIdentifier("gt:FeatureBuffer"); > > DescribeProcessResponse descResponse = wps.issueRequest(descRequest); > ProcessDescriptionsType processDesc = descResponse.getProcessDesc(); > > The problem is, the variable processDesc is null. The descResponse haven't a > valid ProcessDescriptionType. > > I did this request on my > browser:http://localhost:8080/geoserver/ows?service=WPS&request=DescribeProcess&identifier=gt:Union. > I got the right response, then Geoserver WPS Server is OK. > > sWhen I debug the WPS Geotools Module, I found the problem. The method > getOperationURL on WebProcessingService class, line 279, was returning the > wrong URL, > http://localhost:8080/geoserver/?service=wps&request=DescribeProcess&;, then > the request doesn't work. > > I will try solve this problem, removing the getOperationURL call and setting > onlineResource = serverURL. > There is another way to solve it ? Where is it getting the wrong value from? Was it something being returned incorrectly from geoserver? Or is it being parsed incorrectly. The geoOperationURL should be returned as part of the GetCapabilities document. > > Thanks, > Leandro Leal > ------------------------------------------------------------------------------ > _______________________________________________ > Geotools-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-devel
------------------------------------------------------------------------------
_______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
