JOpera for Eclipse

Hello I try to use one of web service(web service only add two numbers and return the result), which JOpera have deployed on http://localhost:8080/wsdl
I call it from Java but I have exception: "Execution failed. Exception: (400)HTTP+method+POST+is+not+supported+by+this+URL"

My Java code to call the web service look like this:

try {
String endpoint = "http://localhost:8080/wsdl?process={ws.localhost.axis.AddFunction.jws}Scitacka[1.0]";
Service service = new Service();
Call call = (Call) service.createCall();

Hello

I'm developing services with JOpera, which seems to me to be a very powerful approach about services composition.

But, I doesn't understand clearly how I can deploy web services based on JOpera.
I'm developing services under Windows and have web server under Linux; can I deploy a JOpera engine on my APache/Tomcat under Eclipse?

Jean-Claude Moissinac

I'm a trying to define a process which use a WSDL
I've copied a sample one in an accessible place
http://paam-itengine.appspot.com/Text.wsdl

This WSDL is well used by a BPEL process in ODE and seems to be correct in the XMethods analyser.

Following the Web Service Tutorial, I'm in the 4.6 step. But when I try to drag a 'program' -here 'SOAP_translate'- in my process, nothing happens.

Any idea?

I try to use simple web service but when i try to run a proccess with web service i have this exception:

SEVERE: Method Parameter: return cannot be null. This is BP 1.1 R2211 violation.
javax.xml.ws.WebServiceException: Method Parameter: return cannot be null. This is BP 1.1 R2211 violation.

I use web service with this wsdl:

http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.6 in JDK 6.
-->
−
http://jax-ws.dev.java.net. RI's version is JAX-WS RI 2.1.6 in JDK 6.
-->
−

New Features:

• standalone JOpera server
• FILE_WRITE adapter, write/append text files from JOpera programs

Updates:

• REST API extended to produce application/atom+xml feeds
• REST API supports server-side filtering with URL wildcards
• Deploy/Undeploy processes by simply adding or removing .oml files from the server workspace
• Starting a JOpera server on an empty workspace will now automagically create a JOpera project ready to accept your .oml files