In your deploy.xml you have two types of partnerlink invocation: one is a provide, the other is an invoke e.g.:
<provide partnerLink="fooPL"> <service name="foo:FooService" port="FooEndpoint"/> </provide> <invoke partnerLink="barPL"> <service name="bar:BarService" port="BarEndpoint"/> </invoke> As I understand it the Ode service engine will try and activate all endpoints that you have defined as "provide". If you are consuming a service already on the bus your deploy should refer to it as an "invoke" partnerlink. Mike. On 7/24/07, jbi joe <[EMAIL PROTECTED]> wrote:
Im gettin an endpoint already defined debug message when deploying a bpel process that includes a wsdl to a service Assembly that has been already deployed to my JBI ESB ( servicemix ) The assembly is deployed bound to lw-component. I would like to have the bpel invoke it. I dont see any examples quite like this, however I would assume an endpoint is an endpoint no matter where it originiates from.. My deploy.xml file includes a reference to the partnerlink spec'd in the wsdl. Can anyone give me clues to what Im doing wrong? I have tons of debug.. When I take out the reference in the deploy.xml, I get a message from the bpel debug that I have an uninitalized partnerlink... Are there any examples that I can see that show this scenario?? Looking at the JBI examples, Ping/Pong HelloWorld, dont fit.. Any help greatly appreciated TIA.. -- View this message in context: http://www.nabble.com/Endpoint-already-defined-tf4135991.html#a11763035 Sent from the Apache Ode User mailing list archive at Nabble.com.
