You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by Sunita Kumari Patro <su...@bcgi.net> on 2007/09/18 14:13:31 UTC
help to convert the bpel workflow designed in activeBpel to ODE
Hi,
I am very new to ODE. I am familiar with Active Endpoint's activeBpel.
In my project we are planning to use ODE bpel workflows.
Can you please guide how I can convert my workflow which is prepared and
running with activeBpel engine, can run with ODE engine running on
servicemix.
Thanks
Sunita
-----------------------------------------
The information contained in this e-mail message and any
attachments is confidential, and is intended only for the use of
the party to whom it is addressed. If you are not the above-named
intended recipient, you are hereby notified that any dissemination,
copying or disclosure of this communication is strictly prohibited.
If you have received this communication in error, please notify
Boston Communications Group, Inc. immediately by reply to this
message or by telephoning (781) 904-5000, and destroy this message
and its attachments, without making any copy or distribution.
Re: help to convert the bpel workflow designed in activeBpel to ODE
Posted by patrosk <su...@rediffmail.com>.
Matthieu,
I am starting the process with the same message you mentioned,
Just to test, I changed the BPEL process to document/lieral. Now the Bpel
process is invoking the outside service running on different instance of
tomcat.
On ODE-tomcat console am getting exception, FORMAT_ERROR description=SOAP
body does not contain expected part wrapper: service
{urn:/HelloWorld.wsdl}HelloWorldService port HelloWorld wrapper
{http://localhost:8085/axis/HelloWorld.jws}sayHiResponse
DEBUG - GeronimoLog.debug(66) | Invoking a partner operation: sayHi
DEBUG - GeronimoLog.debug(66) | The service to invoke is the external
service or
g.apache.ode.axis2.ExternalService@135707c
DEBUG - GeronimoLog.debug(66) | Resolving endpoint reference <?xml
version="1.0"
encoding="UTF-8"?>
<service-ref
xmlns="http://docs.oasis-open.org/wsbpel/2.0/serviceref"><EndpointR
eference xmlns="http://www.w3.org/2005/08/addressing"><Metadata><ServiceName
xml
ns="http://www.w3.org/2006/05/addressing/wsdl" EndpointName="HelloWorld"
xmlns:s
ervicens="urn:/HelloWorld.wsdl">servicens:HelloWorldService</ServiceName></Metad
ata><Address>http://localhost:8085/axis/HelloWorld.jws</Address></EndpointRefere
nce></service-ref>
DEBUG - GeronimoLog.debug(66) | GET MEX property
org.apache.ode.bpel.partnerRole
SessionId = null
DEBUG - GeronimoLog.debug(66) | GET MEX property
org.apache.ode.bpel.myRoleSessi
onId = null
DEBUG - GeronimoLog.debug(66) | My-Role EPR not specified, SEP will not be
used.
DEBUG - GeronimoLog.debug(66) | Axis2 sending message to
http://localhost:8085/a
xis/HelloWorld.jws using MEX {PartnerRoleMex#hqejbhcnphr2ma2mnh1gso [PID
{urn:/t
est2.bpel}test2-11] calling
org.apache.ode.bpel.epr.WSAEndpoint@1ccf342.sayHi(..
.)}
DEBUG - GeronimoLog.debug(66) | Message: <?xml version='1.0'
encoding='utf-8'?><
soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soap
env:Body><axis2ns1:sayHi
xmlns:axis2ns1="http://DefaultNamespace"><str>kavi</str
></axis2ns1:sayHi></soapenv:Body></soapenv:Envelope>
DEBUG - GeronimoLog.debug(66) | replyAsync mex=hqejbhcnphr2ma2mnh1gso
DEBUG - GeronimoLog.debug(66) | Setting execution state on instance 402
DEBUG - GeronimoLog.debug(66) | Sending stateful TO epr in message header
using
session null
DEBUG - GeronimoLog.debug(66) | Sending a message containing wsa endpoints
in he
aders for session passing.
DEBUG - GeronimoLog.debug(66) | <?xml version='1.0'
encoding='utf-8'?><soapenv:E
nvelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Heade
r><addr:To
xmlns:addr="http://www.w3.org/2005/08/addressing">http://localhost:80
85/axis/HelloWorld.jws</addr:To><addr:Action
xmlns:addr="http://www.w3.org/2005/
08/addressing"></addr:Action><addr:ReplyTo
xmlns:addr="http://www.w3.org/2005/08
/addressing"><addr:Address>http://www.w3.org/2005/08/addressing/anonymous</addr:
Address></addr:ReplyTo><addr:MessageID
xmlns:addr="http://www.w3.org/2005/08/add
ressing">uuid:hqejbhcnphr2ma2mnh1gsp</addr:MessageID></soapenv:Header><soapenv:B
ody><axis2ns1:sayHi
xmlns:axis2ns1="http://DefaultNamespace"><str>kavi</str></ax
is2ns1:sayHi></soapenv:Body></soapenv:Envelope>
DEBUG - GeronimoLog.debug(66) | replyWithFailure mex=hqejbhcnphr2ma2mnh1gso
fail
ureType=FORMAT_ERROR description=SOAP body does not contain expected part
wrappe
r: service {urn:/HelloWorld.wsdl}HelloWorldService port HelloWorld wrapper
{http
://localhost:8085/axis/HelloWorld.jws}sayHiResponse details=null
DEBUG - GeronimoLog.debug(66) | create work event for
mex=hqejbhcnphr2ma2mnh1gso
Is it the problem because the outside service"HelloWorldService" which is
being invoked my "test2" BPELprocess is using rpc/encoded pattern.
For reference here are the 2 wsdls.
Here is the wsdls, "test2.wsdl"
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="test2" targetNamespace="urn:/test2.wsdl"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tns="urn:/test2.wsdl"
xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/"
xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://schemas.xmlsoap.org/wsdl/">
<types>
<schema targetNamespace="urn:/test2.wsdl"
xmlns="http://www.w3.org/2001/XMLSchema">
<element name="Request">
<complexType>
<sequence>
<element name="input" type="string"/>
</sequence>
</complexType>
</element>
<element name="Response">
<complexType>
<sequence>
<element name="result" type="string"/>
</sequence>
</complexType>
</element>
</schema>
</types>
<message name="OutputMessage">
<part name="payload" element="tns:Response"/>
</message>
<message name="InputMessage">
<part name="payload" element="tns:Request"/>
</message>
<portType name="HelloWorldWFCallerPT">
<operation name="JobSubmit">
<input message="tns:InputMessage" name="TestInput"/>
<output message="tns:OutputMessage" name="TestOutput"/>
</operation>
</portType>
<binding name="Test2SoapBinding" type="tns:HelloWorldWFCallerPT">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="JobSubmit">
<soap:operation soapAction="" style="document"/>
<input>
<soap:body namespace="urn:/test2.wsdl" use="literal"/>
</input>
<output>
<soap:body namespace="urn:/test2.wsdl" use="literal"/>
</output>
</operation>
</binding>
<service name="Test2Service">
<port name="Test2Port" binding="tns:Test2SoapBinding">
<soap:address
location="http://localhost:8090/ode/processes/test2"/>
</port>
</service>
<plnk:partnerLinkType name="HelloWorldWFCaller">
<plnk:role name="HelloWorldWFCaller"
portType="tns:HelloWorldWFCallerPT"/>
</plnk:partnerLinkType>
</definitions>
External service "helloWorldService"
<?xml version="1.0" encoding="UTF-8" ?>
<wsdl:definitions targetNamespace="urn:/HelloWorld.wsdl"
xmlns:apachesoap="http://xml.apache.org/xml-soap"
xmlns:impl="urn:/HelloWorld.wsdl"
xmlns:intf="http://localhost:8085/axis/HelloWorld.jws"
xmlns:plnk="http://docs.oasis-open.org/wsbpel/2.0/plnktype"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:smix="http://servicemix.org/wsdl/jbi/"
xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<!--
WSDL created by Apache Axis version: 1.3
Built on Oct 05, 2005 (05:23:37 EDT)
-->
<wsdl:message name="sayHiRequest">
<wsdl:part name="str" type="xsd:string" />
</wsdl:message>
<wsdl:message name="sayHiResponse">
<wsdl:part name="sayHiReturn" type="xsd:string" />
</wsdl:message>
<wsdl:portType name="HelloWorld">
<wsdl:operation name="sayHi" parameterOrder="str">
<wsdl:input message="impl:sayHiRequest" name="sayHiRequest" />
<wsdl:output message="impl:sayHiResponse" name="sayHiResponse" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="HelloWorldSoapBinding" type="impl:HelloWorld">
<wsdlsoap:binding style="rpc"
transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="sayHi">
<wsdlsoap:operation soapAction="" />
<wsdl:input name="sayHiRequest">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://DefaultNamespace" use="encoded" />
</wsdl:input>
<wsdl:output name="sayHiResponse">
<wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"
namespace="http://localhost:8085/axis/HelloWorld.jws" use="encoded" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="HelloWorldService">
<wsdl:port binding="impl:HelloWorldSoapBinding" name="HelloWorld">
<wsdlsoap:address location="http://localhost:8085/axis/HelloWorld.jws" />
<!-- <smix:endpoint role="provider" defaultMep="in-out"/>-->
</wsdl:port>
</wsdl:service>
<!-- partnerLinkType defined -->
<plnk:partnerLinkType name="HelloWorldPLT">
<plnk:role name="HelloWorldRole" portType="impl:HelloWorld"/>
</plnk:partnerLinkType>
</wsdl:definitions>
If you could point out where am I going wrong, it'll be of great help to me.
Thanks a lot..
Matthieu Riou-5 wrote:
>
> Looks like there's a problem with the message you're sending to start the
> process. How does it look like? Normally it should be something like:
>
> <SOAP-ENV:Envelope
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/
> ">
> <SOAP-ENV:Body>
> <ns1:JobSubmit xmlns:ns1="urn:/test2.wsdl">
> <hellostring>Hello</hellostring>
> </ns1:JobSubmit>
> </SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
>
> Note that it's not an ODE specificity, that's what is mandated by
> WS-BasicProfile. Also I don't know how many processes you have and how
> large
> they are but you might want to partially redesign them to avoid
> generalizing
> the usage of links. ODE doesn't care much but processes with a lot of
> links
> all over the place is not the easiest thing to maintain.
>
> Cheers,
> Matthieu
>
> On 9/23/07, patrosk <su...@rediffmail.com> wrote:
>>
>>
>> Hi Matthieu,
>>
>> Thanks for replying.
>> I have a BPELprocess running on activeBPEL. Same i am trying run on
>> ODE(running on Tomcat). My "test2-process" is invoking a axis web service
>> which is running on a different instance of tomcat.
>>
>> I am attching here my code test2-process.zip
>> http://www.nabble.com/file/p12854046/test2-process.zip test2-process.zip
>> .
>> It deploys fine, but when i invoke, following exception comes,
>>
>> Sep 21, 2007 6:28:58 PM org.apache.catalina.startup.Catalina start
>> INFO: Server startup in 18222 ms
>> DEBUG - GeronimoLog.debug(66) | The system is checking for the operation
>> using t
>> he following WSAAction: ""
>> DEBUG - GeronimoLog.debug(66) | Checking for Operation using SOAP message
>> body's
>> first child's local name : JobSubmit
>> DEBUG - GeronimoLog.debug(66) | Found operation
>> org.apache.axis2.description.InO
>> utAxisOperation@190ffa7
>> DEBUG - GeronimoLog.debug(66) | Received request message for
>> test2.{urn:/test2.w
>> sdl}JobSubmit
>> DEBUG - GeronimoLog.debug(66) | Starting transaction.
>> DEBUG - GeronimoLog.debug(66) | Routed: svcQname
>> {urn:/test2.wsdl}Test2Service -
>> -> BpelProcess[{urn:/test2.bpel}test2-4]
>> DEBUG - GeronimoLog.debug(66) | ODE routed to operation Operation:
>> name=JobSubmi
>> t
>> style=REQUEST_RESPONSE,1
>> Input: name=TestInput
>> Message: name={urn:/test2.wsdl}InputMessage
>> Part: name=hellostring
>> typeName={http://www.w3.org/2001/XMLSchema}string
>> Output: name=TestOutput
>> Message: name={urn:/test2.wsdl}OutputMessage
>> Part: name=result
>> typeName={http://www.w3.org/2001/XMLSchema}string from service
>> {urn:/test2.wsdl}
>> Test2Service
>> ERROR - GeronimoLog.error(108) | Exception occured while invoking ODE
>> org.apache.ode.axis2.OdeFault: SOAP body does not contain expected part
>> wrapper:
>> service {urn:/test2.wsdl}Test2Service port Test2Port wrapper JobSubmit
>> at
>> org.apache.ode.axis2.util.SoapMessageConverter.extractSoapBodyParts(S
>> oapMessageConverter.java:369)
>> at
>> org.apache.ode.axis2.util.SoapMessageConverter.parseSoapRequest(SoapM
>> essageConverter.java:303)
>> at
>> org.apache.ode.axis2.ODEService.onAxisMessageExchange(ODEService.java
>> :107)
>> at
>> org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODE
>> MessageReceiver.java:69)
>> at
>> org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODE
>> MessageReceiver.java:50)
>> at
>> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMe
>> ssageReceiver.java:96)
>> at
>> org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
>> at
>> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReq
>> uest(HTTPTransportUtils.java:275)
>> at
>> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:1
>> 20)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
>> icationFilterChain.java:290)
>> at
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
>> ilterChain.java:206)
>> at
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
>> alve.java:230)
>> at
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
>> alve.java:175)
>> at
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
>> ava:128)
>> at
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
>> ava:104)
>> at
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
>> ve.java:109)
>> at
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
>> a:261)
>> at
>> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
>> :844)
>> at
>> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
>> ss(Http11Protocol.java:581)
>> at
>> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
>> 7)
>> at java.lang.Thread.run(Thread.java:595)
>>
>> Could you pls help me finding out what is missing in my code..thanks
>>
>>
>>
>> Matthieu Riou-5 wrote:
>> >
>> > On 9/18/07, Sunita Kumari Patro <su...@bcgi.net> wrote:
>> >>
>> >> Hi,
>> >>
>> >>
>> >>
>> >> I am very new to ODE. I am familiar with Active Endpoint's activeBpel.
>> >> In my project we are planning to use ODE bpel workflows.
>> >>
>> >> Can you please guide how I can convert my workflow which is prepared
>> and
>> >> running with activeBpel engine, can run with ODE engine running on
>> >> servicemix.
>> >
>> >
>> > Hi Sunita,
>> >
>> > I was hoping for somebody else with more experience with a similar
>> > conversion to step up as even if I'm very familiar with ODE I don't
>> know
>> > ActiveBPEL that good. Anyway normally your BPEL processes and WSDLs
>> should
>> > be portable, there might be a couple of glitches but hopefully nothing
>> > serious. Then you'll just have to write a small deployment descriptor
>> for
>> > your processes as described in [1].
>> >
>> > For the JBI side it's pretty much like everybody else so you can just
>> > follow
>> > the JBI parts of our user guide. Although if you already have things
>> > working
>> > with standard web services I'd suggest going for a two step process:
>> have
>> > your processes working with ODE in a WS environment and then port the
>> > whole
>> > thing to JBI.
>> >
>> > Cheers,
>> > Matthieu
>> >
>> > [1]
>> http://ode.apache.org/user-guide.html#UserGuide-DeploymentDescriptor
>> >
>> > Thanks
>> >>
>> >> Sunita
>> >>
>> >>
>> >>
>> >>
>> >> -----------------------------------------
>> >> The information contained in this e-mail message and any
>> >> attachments is confidential, and is intended only for the use of
>> >> the party to whom it is addressed. If you are not the above-named
>> >> intended recipient, you are hereby notified that any dissemination,
>> >> copying or disclosure of this communication is strictly prohibited.
>> >> If you have received this communication in error, please notify
>> >> Boston Communications Group, Inc. immediately by reply to this
>> >> message or by telephoning (781) 904-5000, and destroy this message
>> >> and its attachments, without making any copy or distribution.
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/help-to-convert-the-bpel-workflow-designed-in-activeBpel-to-ODE-tf4474832.html#a12854046
>> Sent from the Apache Ode User mailing list archive at Nabble.com.
>>
>>
>
>
--
View this message in context: http://www.nabble.com/help-to-convert-the-bpel-workflow-designed-in-activeBpel-to-ODE-tf4474832.html#a12894418
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: help to convert the bpel workflow designed in activeBpel to ODE
Posted by Matthieu Riou <ma...@offthelip.org>.
Looks like there's a problem with the message you're sending to start the
process. How does it look like? Normally it should be something like:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/
">
<SOAP-ENV:Body>
<ns1:JobSubmit xmlns:ns1="urn:/test2.wsdl">
<hellostring>Hello</hellostring>
</ns1:JobSubmit>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Note that it's not an ODE specificity, that's what is mandated by
WS-BasicProfile. Also I don't know how many processes you have and how large
they are but you might want to partially redesign them to avoid generalizing
the usage of links. ODE doesn't care much but processes with a lot of links
all over the place is not the easiest thing to maintain.
Cheers,
Matthieu
On 9/23/07, patrosk <su...@rediffmail.com> wrote:
>
>
> Hi Matthieu,
>
> Thanks for replying.
> I have a BPELprocess running on activeBPEL. Same i am trying run on
> ODE(running on Tomcat). My "test2-process" is invoking a axis web service
> which is running on a different instance of tomcat.
>
> I am attching here my code test2-process.zip
> http://www.nabble.com/file/p12854046/test2-process.zip test2-process.zip
> .
> It deploys fine, but when i invoke, following exception comes,
>
> Sep 21, 2007 6:28:58 PM org.apache.catalina.startup.Catalina start
> INFO: Server startup in 18222 ms
> DEBUG - GeronimoLog.debug(66) | The system is checking for the operation
> using t
> he following WSAAction: ""
> DEBUG - GeronimoLog.debug(66) | Checking for Operation using SOAP message
> body's
> first child's local name : JobSubmit
> DEBUG - GeronimoLog.debug(66) | Found operation
> org.apache.axis2.description.InO
> utAxisOperation@190ffa7
> DEBUG - GeronimoLog.debug(66) | Received request message for
> test2.{urn:/test2.w
> sdl}JobSubmit
> DEBUG - GeronimoLog.debug(66) | Starting transaction.
> DEBUG - GeronimoLog.debug(66) | Routed: svcQname
> {urn:/test2.wsdl}Test2Service -
> -> BpelProcess[{urn:/test2.bpel}test2-4]
> DEBUG - GeronimoLog.debug(66) | ODE routed to operation Operation:
> name=JobSubmi
> t
> style=REQUEST_RESPONSE,1
> Input: name=TestInput
> Message: name={urn:/test2.wsdl}InputMessage
> Part: name=hellostring
> typeName={http://www.w3.org/2001/XMLSchema}string
> Output: name=TestOutput
> Message: name={urn:/test2.wsdl}OutputMessage
> Part: name=result
> typeName={http://www.w3.org/2001/XMLSchema}string from service
> {urn:/test2.wsdl}
> Test2Service
> ERROR - GeronimoLog.error(108) | Exception occured while invoking ODE
> org.apache.ode.axis2.OdeFault: SOAP body does not contain expected part
> wrapper:
> service {urn:/test2.wsdl}Test2Service port Test2Port wrapper JobSubmit
> at
> org.apache.ode.axis2.util.SoapMessageConverter.extractSoapBodyParts(S
> oapMessageConverter.java:369)
> at
> org.apache.ode.axis2.util.SoapMessageConverter.parseSoapRequest(SoapM
> essageConverter.java:303)
> at
> org.apache.ode.axis2.ODEService.onAxisMessageExchange(ODEService.java
> :107)
> at
> org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODE
> MessageReceiver.java:69)
> at
> org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODE
> MessageReceiver.java:50)
> at
> org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMe
> ssageReceiver.java:96)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReq
> uest(HTTPTransportUtils.java:275)
> at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:1
> 20)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
> icationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
> ilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
> alve.java:230)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
> alve.java:175)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
> ava:128)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
> ava:104)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
> ve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
> a:261)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
> :844)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
> ss(Http11Protocol.java:581)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
> 7)
> at java.lang.Thread.run(Thread.java:595)
>
> Could you pls help me finding out what is missing in my code..thanks
>
>
>
> Matthieu Riou-5 wrote:
> >
> > On 9/18/07, Sunita Kumari Patro <su...@bcgi.net> wrote:
> >>
> >> Hi,
> >>
> >>
> >>
> >> I am very new to ODE. I am familiar with Active Endpoint's activeBpel.
> >> In my project we are planning to use ODE bpel workflows.
> >>
> >> Can you please guide how I can convert my workflow which is prepared
> and
> >> running with activeBpel engine, can run with ODE engine running on
> >> servicemix.
> >
> >
> > Hi Sunita,
> >
> > I was hoping for somebody else with more experience with a similar
> > conversion to step up as even if I'm very familiar with ODE I don't know
> > ActiveBPEL that good. Anyway normally your BPEL processes and WSDLs
> should
> > be portable, there might be a couple of glitches but hopefully nothing
> > serious. Then you'll just have to write a small deployment descriptor
> for
> > your processes as described in [1].
> >
> > For the JBI side it's pretty much like everybody else so you can just
> > follow
> > the JBI parts of our user guide. Although if you already have things
> > working
> > with standard web services I'd suggest going for a two step process:
> have
> > your processes working with ODE in a WS environment and then port the
> > whole
> > thing to JBI.
> >
> > Cheers,
> > Matthieu
> >
> > [1] http://ode.apache.org/user-guide.html#UserGuide-DeploymentDescriptor
> >
> > Thanks
> >>
> >> Sunita
> >>
> >>
> >>
> >>
> >> -----------------------------------------
> >> The information contained in this e-mail message and any
> >> attachments is confidential, and is intended only for the use of
> >> the party to whom it is addressed. If you are not the above-named
> >> intended recipient, you are hereby notified that any dissemination,
> >> copying or disclosure of this communication is strictly prohibited.
> >> If you have received this communication in error, please notify
> >> Boston Communications Group, Inc. immediately by reply to this
> >> message or by telephoning (781) 904-5000, and destroy this message
> >> and its attachments, without making any copy or distribution.
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/help-to-convert-the-bpel-workflow-designed-in-activeBpel-to-ODE-tf4474832.html#a12854046
> Sent from the Apache Ode User mailing list archive at Nabble.com.
>
>
Re: help to convert the bpel workflow designed in activeBpel to ODE
Posted by patrosk <su...@rediffmail.com>.
Hi Matthieu,
Thanks for replying.
I have a BPELprocess running on activeBPEL. Same i am trying run on
ODE(running on Tomcat). My "test2-process" is invoking a axis web service
which is running on a different instance of tomcat.
I am attching here my code test2-process.zip
http://www.nabble.com/file/p12854046/test2-process.zip test2-process.zip .
It deploys fine, but when i invoke, following exception comes,
Sep 21, 2007 6:28:58 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 18222 ms
DEBUG - GeronimoLog.debug(66) | The system is checking for the operation
using t
he following WSAAction: ""
DEBUG - GeronimoLog.debug(66) | Checking for Operation using SOAP message
body's
first child's local name : JobSubmit
DEBUG - GeronimoLog.debug(66) | Found operation
org.apache.axis2.description.InO
utAxisOperation@190ffa7
DEBUG - GeronimoLog.debug(66) | Received request message for
test2.{urn:/test2.w
sdl}JobSubmit
DEBUG - GeronimoLog.debug(66) | Starting transaction.
DEBUG - GeronimoLog.debug(66) | Routed: svcQname
{urn:/test2.wsdl}Test2Service -
-> BpelProcess[{urn:/test2.bpel}test2-4]
DEBUG - GeronimoLog.debug(66) | ODE routed to operation Operation:
name=JobSubmi
t
style=REQUEST_RESPONSE,1
Input: name=TestInput
Message: name={urn:/test2.wsdl}InputMessage
Part: name=hellostring
typeName={http://www.w3.org/2001/XMLSchema}string
Output: name=TestOutput
Message: name={urn:/test2.wsdl}OutputMessage
Part: name=result
typeName={http://www.w3.org/2001/XMLSchema}string from service
{urn:/test2.wsdl}
Test2Service
ERROR - GeronimoLog.error(108) | Exception occured while invoking ODE
org.apache.ode.axis2.OdeFault: SOAP body does not contain expected part
wrapper:
service {urn:/test2.wsdl}Test2Service port Test2Port wrapper JobSubmit
at
org.apache.ode.axis2.util.SoapMessageConverter.extractSoapBodyParts(S
oapMessageConverter.java:369)
at
org.apache.ode.axis2.util.SoapMessageConverter.parseSoapRequest(SoapM
essageConverter.java:303)
at
org.apache.ode.axis2.ODEService.onAxisMessageExchange(ODEService.java
:107)
at
org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODE
MessageReceiver.java:69)
at
org.apache.ode.axis2.hooks.ODEMessageReceiver.invokeBusinessLogic(ODE
MessageReceiver.java:50)
at
org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMe
ssageReceiver.java:96)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
at
org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostReq
uest(HTTPTransportUtils.java:275)
at
org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:1
20)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Appl
icationFilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationF
ilterChain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperV
alve.java:230)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextV
alve.java:175)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:128)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:104)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:261)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ss(Http11Protocol.java:581)
at
org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
7)
at java.lang.Thread.run(Thread.java:595)
Could you pls help me finding out what is missing in my code..thanks
Matthieu Riou-5 wrote:
>
> On 9/18/07, Sunita Kumari Patro <su...@bcgi.net> wrote:
>>
>> Hi,
>>
>>
>>
>> I am very new to ODE. I am familiar with Active Endpoint's activeBpel.
>> In my project we are planning to use ODE bpel workflows.
>>
>> Can you please guide how I can convert my workflow which is prepared and
>> running with activeBpel engine, can run with ODE engine running on
>> servicemix.
>
>
> Hi Sunita,
>
> I was hoping for somebody else with more experience with a similar
> conversion to step up as even if I'm very familiar with ODE I don't know
> ActiveBPEL that good. Anyway normally your BPEL processes and WSDLs should
> be portable, there might be a couple of glitches but hopefully nothing
> serious. Then you'll just have to write a small deployment descriptor for
> your processes as described in [1].
>
> For the JBI side it's pretty much like everybody else so you can just
> follow
> the JBI parts of our user guide. Although if you already have things
> working
> with standard web services I'd suggest going for a two step process: have
> your processes working with ODE in a WS environment and then port the
> whole
> thing to JBI.
>
> Cheers,
> Matthieu
>
> [1] http://ode.apache.org/user-guide.html#UserGuide-DeploymentDescriptor
>
> Thanks
>>
>> Sunita
>>
>>
>>
>>
>> -----------------------------------------
>> The information contained in this e-mail message and any
>> attachments is confidential, and is intended only for the use of
>> the party to whom it is addressed. If you are not the above-named
>> intended recipient, you are hereby notified that any dissemination,
>> copying or disclosure of this communication is strictly prohibited.
>> If you have received this communication in error, please notify
>> Boston Communications Group, Inc. immediately by reply to this
>> message or by telephoning (781) 904-5000, and destroy this message
>> and its attachments, without making any copy or distribution.
>
>
--
View this message in context: http://www.nabble.com/help-to-convert-the-bpel-workflow-designed-in-activeBpel-to-ODE-tf4474832.html#a12854046
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: help to convert the bpel workflow designed in activeBpel to ODE
Posted by Matthieu Riou <ma...@offthelip.org>.
On 9/18/07, Sunita Kumari Patro <su...@bcgi.net> wrote:
>
> Hi,
>
>
>
> I am very new to ODE. I am familiar with Active Endpoint's activeBpel.
> In my project we are planning to use ODE bpel workflows.
>
> Can you please guide how I can convert my workflow which is prepared and
> running with activeBpel engine, can run with ODE engine running on
> servicemix.
Hi Sunita,
I was hoping for somebody else with more experience with a similar
conversion to step up as even if I'm very familiar with ODE I don't know
ActiveBPEL that good. Anyway normally your BPEL processes and WSDLs should
be portable, there might be a couple of glitches but hopefully nothing
serious. Then you'll just have to write a small deployment descriptor for
your processes as described in [1].
For the JBI side it's pretty much like everybody else so you can just follow
the JBI parts of our user guide. Although if you already have things working
with standard web services I'd suggest going for a two step process: have
your processes working with ODE in a WS environment and then port the whole
thing to JBI.
Cheers,
Matthieu
[1] http://ode.apache.org/user-guide.html#UserGuide-DeploymentDescriptor
Thanks
>
> Sunita
>
>
>
>
> -----------------------------------------
> The information contained in this e-mail message and any
> attachments is confidential, and is intended only for the use of
> the party to whom it is addressed. If you are not the above-named
> intended recipient, you are hereby notified that any dissemination,
> copying or disclosure of this communication is strictly prohibited.
> If you have received this communication in error, please notify
> Boston Communications Group, Inc. immediately by reply to this
> message or by telephoning (781) 904-5000, and destroy this message
> and its attachments, without making any copy or distribution.