Hello thanx for your help ..All of you...

I am trying with BPELtest.java...(as quoted by Lance Waterman )

I have imported everything into eclipse...(ie the entire folder " Bpel-test
" )

Also i have added the required Jar's for that (ie  ode\bpel-api\target\ode-
bpel-api-2.0-SNAPSHOT.jar)

I have started Tomcat...with ODE engine in it

Now eclipse throws some errors/problems :

1) The project was not built since its build path is incomplete. Cannot find
the class file for javax.wsdl.PortType. Fix the build path then try building
this project  [Resource :  BPELTest  ]

2) The type javax.wsdl.PortType cannot be resolved. It is indirectly
referenced from required .class files
[ Resource : MessageExchangeContextImpl.java    Path:
BPELTest/org/apache/ode/test ]



I couldnt understand what else is required....?

Would be glad if someone can give me some info on tthis..


Sam..










On 11/2/06, Vo, Khanh <[EMAIL PROTECTED]> wrote:

You can also use Axis'2 wsdl2java to generate the java client.

-----Original Message-----
From: Paul Brown [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 02, 2006 8:32 AM
To: [email protected]
Subject: Re: How to access ODE process from a Java Client ?

Hi, Sam --

To add to what Lance said:

> Is there someother way to access the BPEL process other than sending
SOAP
> messages  ?

The way that one access any BPEL engine is by sending WSDL messages,
where both "send" and "message" are in the abstract sense.  SOAP over
HTTP is just one implementation of that combination of operations
(XML out of bits on the wire into WSDL structure).

> I saw this code  for ActiveBPEL  in  their website ?
[...]
>        Call call = (Call) service.createCall();
[...]
> Do we have some thing like that in Apache ODE to access the HelloWorld
BPEL
> process ?

This is just an Apache AXIS web service client invocation and an
RPC-style one at that, and the availability of this kind of API is
really just a consequence of the BPEL engine being deployed as a web
service that accepts the kind of SOAP that the client (the Call) spits
out.  You could use the *exact* same approach with an appropriate
deployment of ODE.

-- Paul

Reply via email to