Hey Pablo,
The python scripting stuff doesn't come by default with the wps module, so
if building from sources you'll have to enable it separately. Instead build
with this command.
mvn clean install -P wps,script,script-py
That should enable the basic scripting functionality plus the python
runtime.
-Justin
On Mon, May 5, 2014 at 9:00 AM, pablo zader <pza...@gmail.com> wrote:
> *Hi list:*
>
> *I'm trying to run python script done through WPS but geoserver does not
> recognize the existence of geoprocesses I created.*
>
> *I'm following the instructions:*
>
> http://docs.geoserver.org/stable/en/user/community/scripting/py/index.html
>
> http://suite.opengeo.org/docs/latest/processing/scripting/processcreate.html
>
> *When I make a GetCapabilities* (
> http://localhost:8080/geoserver/ows?service=wps&version=1.0.0&request=GetCapabilities),
> get the list of all who are part of geoprocesses geoserver (gs.*, geo.*,
> vec.*, ras.*, JTS.*,gt.*) but none of them is py.*
>
> *When I run a DescribeProcess* (
> http://localhost:8080/geoserver/ows?service=WPS&version=1.0.0&request=DescribeProcess&identifier=py:distbear
> )
> get the next response:
>
> <ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows/1.1"; xmlns:xsi
> ="http://www.w3.org/2001/XMLSchema-instance"; version="1.1.0"
> xsi:schemaLocation="http://www.opengis.net/ows/1.1
> http://localhost:8080/geoserver/schemas/ows/1.1.0/owsAll.xsd";>
> <ows:Exception exceptionCode="NoApplicableCode">
> <ows:ExceptionText>No such process: py:distbear</ows:ExceptionText>
> </ows:Exception>
> </ows:ExceptionReport>
>
> *and the log of the geoserver reports:*
>
> 2014-05-05 11:50:12,296 WARN [geoserver.ows] - Could not get a ServiceInfo
> for service wps thus could not check if the service is enabled
> 2014-05-05 11:50:12,298 ERROR [geoserver.ows] -
> org.geoserver.wps.WPSException: No such process: py:distbear
> at
> org.geoserver.wps.DescribeProcess.processDescription(DescribeProcess.java:106)
> at org.geoserver.wps.DescribeProcess.run(DescribeProcess.java:96)
> at
> org.geoserver.wps.DefaultWebProcessingService.describeProcess(DefaultWebProcessingService.java:69)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:622)
> at
> org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:318)
> ....
> *If for exmaple i do describeprocess of JTS:buffer:*
>
> http://localhost:8080/geoserver/ows?service=WPS&version=1.0.0&request=DescribeProcess&identifier=JTS:buffer
> *this works fine and works well for any pre-existing geoprocessing in
> geoserver.*
>
> *My geoserver was compiled with*:
> mvn clean install -Pwps
>
> *The version I'm using is* : (geoserver and tomcat)
> Versión:2.4-SNAPSHOT
> Revisión de Git: ea0d7c50695f6c2a4564fc5f8fceb1c0b6eb543a
> Fecha de compilación :21-Mar-2014 19:03
> Versión de GeoTools :10-SNAPSHOT (rev
> ff340eb96a28b463470cc79a566f8ed12fab934e)
> Versión GeoWebCache 1.5.0 (rev
> 1.5.x/f981cafd349886bb2a1ef45067f26b1aa8e4aff4)
> Apache Tomcat/6.0.35 JVM: 1.6.0_30-b30-
>
> Appreciate your help!
>
> Cheers
>
> Pablo
>
>
>
>
>
> ------------------------------------------------------------------------------
> Is your legacy SCM system holding you back? Join Perforce May 7 to find
> out:
> • 3 signs your SCM is hindering your productivity
> • Requirements for releasing software faster
> • Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Geoserver-users mailing list
> Geoserver-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>
>
--
*Justin Deoliveira*
Vice President, Engineering | Boundless
jdeol...@boundlessgeo.com
@j_deolive <https://twitter.com/j_deolive>
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
