No ideas? KR Quentin
qdallons wrote: > > > My working use case is: > > A process exposed as a web service outside the bus. My bpel process > orchestrates a call to an external Web Service bind to the bus through a > http-bc JBI endpoint and a second call to a JBI JSR181 Service > > HTTP BC <--> ODE SE <--> 1° HTTP BC <--> External Web Service on tomcat > <--> 2° JSR181 SE > > When I replace the HTTP BC exposing the ODE process by CXF BC, I get the > error described below. > > KR > Quentin > > > > Freeman Fang wrote: >> >> Hi Quentin, >> >> Would you please append the message with your working env (http-bc --> >> ode ). >> Thanks >> >> Freeman >> >> qdallons wrote: >>> Hi Freeman, >>> >>> ok but what I don't understand is that it works with the HTTP-BC SE >>> which >>> also produces a JBI message. >>> >>> Any ideas? >>> >>> KR >>> Quentin >>> >>> >>> >>> Freeman Fang wrote: >>> >>>> Hi Quentin, >>>> >>>> I am not an expert of Ode BPEL, so I don't know if Ode can only handle >>>> soap message as input? >>>> Since cxf-bc always do the transformation between SOAP message and JBI >>>> message, so the workaround I can suggest is >>>> 1) and transformer (xslt maybe) between the cxf-bc and Ode >>>> 2) maybe we need add an option for cxf-bc to let soap message pass in >>>> and don't change it >>>> >>>> Actually, I don't think 1) and 2) is good suggestion, since I think all >>>> component on the JBI bus should handle the universal JBI message >>>> >>>> Best Regards >>>> >>>> Freeman >>>> >>>> qdallons wrote: >>>> >>>>> Hi Freeman, >>>>> >>>>> thanks for your reply. >>>>> Now, my following question is: any idea how to fix/workaround this to >>>>> achieve my goal (exposing Ode BPEL process with a cxf-bc). >>>>> Also, another question is: Is the cxf-bc behavior incorrect or Ode JBI >>>>> behavior. >>>>> >>>>> KR >>>>> Quentin >>>>> >>>>> >>>>> >>>>> Freeman Fang wrote: >>>>> >>>>> >>>>>> Hi Quentin, >>>>>> >>>>>> Sorry I miss your mail about the cxf-bc working with bpel engine. >>>>>> The cxf-bc will change soap message to jbi message, which use jbi >>>>>> wrapper, something like >>>>>> <jbi:message> >>>>>> ... >>>>>> </jbi:message> >>>>>> I guess that's why your bpel engine can't handle it. >>>>>> >>>>>> Best Regards >>>>>> >>>>>> Freeman >>>>>> >>>>>> >>>>>> On Fri, Feb 15, 2008 at 8:54 PM, qdallons >>>>>> <[EMAIL PROTECTED]> >>>>>> wrote: >>>>>> >>>>>> >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> to expose your BPEL process you need to configure a consumer CXF-BC >>>>>>> su. >>>>>>> >>>>>>> I've tried and it seems cxf-bc is not happy with. See my unreplied >>>>>>> post >>>>>>> here: >>>>>>> >>>>>>> http://www.nabble.com/Problem-exposing-Ode-bpel-as-a-web-service-with-the-cxf-bc-td15286951s12049.html >>>>>>> >>>>>>> You can do it with a http-bc consumer su, in that case the result is >>>>>>> successful. >>>>>>> >>>>>>> KR >>>>>>> Quentin >>>>>>> >>>>>>> >>>>>>> >>>>>>> jhpatti wrote: >>>>>>> >>>>>>> >>>>>>>> I have an existing BPEL process within a BPE su. Is there a way >>>>>>>> to >>>>>>>> access this process through cxf? If so, how. >>>>>>>> >>>>>>>> Thanks. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>> -- >>>>>>> View this message in context: >>>>>>> http://www.nabble.com/CXF-to-BPEL-tp15499345s12049p15500393.html >>>>>>> Sent from the ServiceMix - User mailing list archive at Nabble.com. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>> >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/CXF-to-BPEL-tp15499345s12049p15589013.html Sent from the ServiceMix - User mailing list archive at Nabble.com.
