Yes, that would be good to have a possibility to register one process to FOO#bar1 and another process to FOO#bar2
As a clear advantage of ODE/BPEL approach I see a possibility to encapsulate implementation. One service could be implemented in Java, another one in BPEL and run by ODE, however if in ODE we can only implements services with only one operation that breaks the picture. On 30.03.10 22:24, "Vishal Saxena" <[email protected]> wrote: So you want two initiating receives bar1 and bar2 or bar2 is really just a message that can be received later? Vishal On Tue, Mar 30, 2010 at 1:06 PM, Renat Zubairov <[email protected]>wrote: > No it's actually not a content-based routing. > > Imagine following simple situation you have a service FOO with two > operations "bar1" and "bar2" so basically service FOO has an endpoint which > is for example http://localhost:8080/ode/processes/FOO how can I deploy > two processes, one for "bar1" and second one for "bar2" > > As I understood that's the problem Raidwan mentioned. We also seen the > similar issues when process that implements FOO#bar1 was trying to call > FOO#bar2 which essentially sending message to nowhere, since we haven't > found a way to let ODE implement two operations for service FOO as two > separate processes. > > Renat > > > On 30.03.10 19:33, "Brian Lund" <[email protected]> wrote: > > 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. > > > > > > > -- Vishal Saxena Vice President Engineering Intalio Inc http://vishals.blogspot.com
