It sounds like what you want is content based routing (or maybe just some load balancing/fail over?). In a typical SOA, the ESB or a front-end preceding the BPM would handle that. Do you not have the capability to route messages through a service bus?
If I missed the mark, what's your scenario that you want processes to share an endpoint? On 3/30/10 5:01 AM, "Renat Zubairov" <[email protected]> wrote: > Hi > > We had related issues with Process2Process communication. AFAIK there is no > way for ODE to associate endpoint to multiple processes (here I'm referring to > ODE 1.3.X). I also see this as a severe limitation that affects usability of > the ODE as a BPM runtime in heterogeneous SOA infrastructure. > > Best regards, > Renat Zubairov > > On 30.03.10 11:47, "Raidwan" <[email protected]> wrote: > > > > Hi all, > > Anyone now a solution to get one Wsdl and one endpoint from multiple BPEL > processes ? > > i've got the error : > javax.jbi.JBIException: An internal endpoint for service xxxxxx and endpoint > xxxxxxPort is already registered > > I have tried this : > => one wsdl with multiple operations > => one BPEL process by operation > > Example : > Wsdl with operation opeA, opeB, opeC and one End Point for this wsdl > My deploy.xml is like this: > <process name="procA"> > <active>true</active> > <provide partnerLink="myWsdlPartnerLink"> > <service name="myWsdlService" port="myWsdlPort"/> > </provide> > </process> > <process name="procB"> > <active>true</active> > <provide partnerLink="myWsdlPartnerLink"> > <service name="myWsdlService" port="myWsdlPort"/> > </provide> > </process> > > Thanks for help. > -- > View this message in context: > http://old.nabble.com/One-Wsdl-and-one-endpoint-from-multiple-BPEL-processes-t > p28080175p28080175.html > Sent from the Apache Ode User mailing list archive at Nabble.com. > >
