schema not found

classic Classic list List threaded Threaded
10 messages Options
Reply | Threaded
Open this post in threaded view
|

schema not found

sammeek
Dear Benjamin,

I am using an orchestration engine to compose WPS workflows, however when I try and pass one result to the next, I get:

java.io.FileNotFoundException: http://localhost:8010/wps/schemas/9eb2850d-fb65-4093-a886-8b0437d8f0b1.xsd

Do I need to make /wps/schemas public? Or is there somewhere that I can configure this?

Thanks

Sam
Reply | Threaded
Open this post in threaded view
|

Re: schema not found

BenjaminPross
Hello Sam,

The schemas folder should be public by default. Can you verify that the xsd file exists? Are hostname, port and webapp path correct?

Cheers,

Benjamin
Reply | Threaded
Open this post in threaded view
|

Re: schema not found

sammeek
In reply to this post by sammeek
Can I add that I am attempting to call the wps located on tomcat:

http://localhost:8010/wps/WebprocessingService?

from a webapp on jboss:

http://localhost:8080/webapp

Thanks

Sam
Reply | Threaded
Open this post in threaded view
|

Re: schema not found

sammeek
Hi Benjamin,

I am calling the WPS from the OE running on JBOSS.

The schema exists but in the Orchestration Engine webapp/schemas folder.

Is there a config option somewhere where I can set this?

The schema is being written to:

http://localhost:8080/<webapp>/schemas/

However the WPS client is looking for it at:

http://localhost:8010/wps/schemas/


Thanks

Sam


Reply | Threaded
Open this post in threaded view
|

Re: schema not found

BenjaminPross
Yes, port and webapp path are configurable. You can either manipulate
the parameters in the wps_config.xml (attributes of the Server-element,
quite at the bottom of the file) or set them via the Admin Console.

Cheers,

Benjamin

Am 26.01.2015 um 14:50 schrieb sammeek:

> Hi Benjamin,
>
> I am calling the WPS from the OE running on JBOSS.
>
> The schema exists but in the Orchestration Engine webapp/schemas folder.
>
> Is there a config option somewhere where I can set this?
>
> The schema is being written to:
>
> http://localhost:8080/<webapp>/schemas/
>
> However the WPS client is looking for it at:
>
> http://localhost:8010/wps/schemas/
>
>
> Thanks
>
> Sam
>
>
>
>
>
>
> --
> View this message in context: http://geoprocessing.forum.52north.org/schema-not-found-tp4025990p4025993.html
> Sent from the 52° North - Geoprocessing Community Forum mailing list archive at Nabble.com.
> _______________________________________________
> Geoprocessingservices mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/geoprocessingservices
> http://geoprocessing.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines


--
Benjamin Proß
Software Engineer
52°North Geoprocessing Community

52°North Initiative for Geospatial Open Source Software GmbH
Martin-Luther-King-Weg 24
Fon: +49-(0)-251–396371-42
Fax: +49-(0)-251–396371-11
[hidden email]
http://52north.org/

General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
Local Court Muenster HRB 10849

_______________________________________________
Geoprocessingservices mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/geoprocessingservices
http://geoprocessing.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines
Reply | Threaded
Open this post in threaded view
|

Re: schema not found

sammeek
Hi Benjamin,

Yes, my port and path are configured correctly in wps_geotools_config.xml and the process executes correctly (from server logs). The problem is with the schema that is generated. I am using the client library in a workflow engine, which is then deployed on a server (same machine to the wps, but different application server and obviously a different port). The client library creates WPS requests according to the workflow, however when I try and parse a result on the workflow side, I get the file not found error.

It is as if the schema is being put in the /schema directory of the workflow engine, but the client libraries are looking for the generated schema in the /wps/schema directory.

Any ideas?

thanks

Sam
Reply | Threaded
Open this post in threaded view
|

Re: schema not found

BenjaminPross
I think I found the reason for this issue. The folder to store the schemas is located via the WPSConfig class of the 52n-wps-commons library. This lib is needed for the client api as well, i.e. the library will exist in the WEB-INF/lib folder of the workflow engine. Somehow the path of this WPSConfig class must be used to store the schemas. I am not sure how this could happen though, as you said you are using a different application server for the WPS. I will try to conduct some experiments to prove this behavior.

Cheers,

Benjamin
Reply | Threaded
Open this post in threaded view
|

Re: schema not found

sammeek
Hi Benjamin,

Thank you for your efforts.

A temporary workaround is to simlink the schema folder in the webapp to the workflow schema folder, however this is less than ideal and will cause problems down the line I think.

sam
Reply | Threaded
Open this post in threaded view
|

Re: schema not found

sammeek
Hi Benjamin,

Unfortunately, I have come to a point where this work around will not work.

I am now using a reverse proxy so that the WPS is served through apache (mainly for security reasons). This in turn causes a problem with the schema folder, when I execute a client request, the client seems to be looking for the schemas folder at:

localhost:8000/wps/schemas

when I need it to look for

localhost/wps/schemas

Where is this path defined please? I have changed wps_config.xml to port 80:

<Server hostname="localhost" hostport="80" includeDataInputsInResponse="false" computationTimeoutMilliSeconds="5" cacheCapabilites="false" webappPath="wps" r$
    <Database/>
  </Server>

Thanks

Sam
Reply | Threaded
Open this post in threaded view
|

Re: schema not found

BenjaminPross
Hi Sam,

The WPS still seems to choose a wrong wps_config.xml.
Could you check the capabilities of the WPS?
 From what I understand, it should return
localhost:80/wps/WebProcessingService for the GET/POST URLs.

Cheers,

Benjamin

Am 24.03.2015 um 16:14 schrieb sammeek:

> Hi Benjamin,
>
> Unfortunately, I have come to a point where this work around will not work.
>
> I am now using a reverse proxy so that the WPS is served through apache
> (mainly for security reasons). This in turn causes a problem with the schema
> folder, when I execute a client request, the client seems to be looking for
> the schemas folder at:
>
> localhost:8000/wps/schemas
>
> when I need it to look for
>
> localhost/wps/schemas
>
> Where is this path defined please? I have changed wps_config.xml to port 80:
>
> <Server hostname="localhost" hostport="80"
> includeDataInputsInResponse="false" computationTimeoutMilliSeconds="5"
> cacheCapabilites="false" webappPath="wps" r$
>      <Database/>
>    </Server>
>
> Thanks
>
> Sam
>
>
>
>
> --
> View this message in context: http://geoprocessing.forum.52north.org/schema-not-found-tp4025990p4026019.html
> Sent from the 52° North - Geoprocessing Community Forum mailing list archive at Nabble.com.
> _______________________________________________
> Geoprocessingservices mailing list
> [hidden email]
> http://list.52north.org/mailman/listinfo/geoprocessingservices
> http://geoprocessing.forum.52north.org
> Please respect our mailing list guidelines:
> http://52north.org/resources/mailing-lists-and-forums/guidelines


--
Benjamin Proß
Software Engineer
52°North Geoprocessing Community

52°North Initiative for Geospatial Open Source Software GmbH
Martin-Luther-King-Weg 24
Fon: +49-(0)-251–396371-42
Fax: +49-(0)-251–396371-11
[hidden email]
http://52north.org/

General Managers: Dr. Albert Remke, Dr. Andreas Wytzisk
Local Court Muenster HRB 10849

_______________________________________________
Geoprocessingservices mailing list
[hidden email]
http://list.52north.org/mailman/listinfo/geoprocessingservices
http://geoprocessing.forum.52north.org
Please respect our mailing list guidelines:
http://52north.org/resources/mailing-lists-and-forums/guidelines