Well, I'm not too surprised about that. You should try to use the jbi wrapper everywhere, either using cxf-bc or the new <http:soap-consumer /> endpoints :-(
On Fri, Feb 22, 2008 at 9:14 AM, qdallons <[EMAIL PROTECTED]> wrote: > > Hi Guillaume, > > I've posted the question on the Ode user list and here is the answer from > Alex Boisvert: > > On 2/21/08, Quentin Dallons <[EMAIL PROTECTED]> wrote: > > > > I have a problem with that fact because it forces me to change already > > deployed configurations (1° needs to be migrate to CXF-BC) in order to > > make > > them compatible with the Ode message mapping choice. This issue makes me > > rise the following question: how can Ode JBI face complex situations > > (configurations) like my UC if it only can handle one message mapper at a > > time? > > > The cynical answer to this is that message mediation is precisely the reason > of being of JBI. Mediation should happen at the bus level (with or without > binding component), not within service engines. There's no reason to > reinvent routing, transformation, mediation, and so on, within Ode if > there's a better, more general framework for doing it. > > We provided different message mappers as convenience and to get things > working initially. Personally, I don't think adding more features like this > in Ode as being a good thing to do. I would rather submit patches to > ServiceMix to push this kind of feature into the bus. > > My $0.02, > alex > > > KR > Quentin > > > > > > > > gnodet wrote: > > > > This is a limitation of Ode currently. > > This question could be raise on the Ode list I suppose. > > > > On Thu, Feb 21, 2008 at 12:36 PM, qdallons > > <[EMAIL PROTECTED]> wrote: > >> > >> Hi Guillaume, > >> > >> I've putted smx in debug mode, it seems the error comes from the > >> incovcation > >> of a JBI endpoint inside my Bpel process (1°) which still uses a > >> http-bc. > >> > >> Reminder of my UC: > >> CXF BC <--> ODE SE <--> 1° HTTP BC <--> External Web Service on tomcat > >> <--> 2° JSR181 SE > >> > >> In a way it's quite logical that my ODE which speaks only > >> WrapperdWDSL11 > >> cannot speaks correctly ServiceMix or DocLit. > >> > >> I'm busy right now but I'll test to change the http-bc in cxf later to > >> see > >> if everything is ok. > >> > >> But this issue makes me rise the following question: how can ode jbi > >> face > >> complex situation (configuration) like my UC if it only can handle one > >> mapper at a time? > >> > >> KR > >> Quentin > >> > >> > >> > >> > >> > >> The WSDL11Wrapper should work and if there is any problem, it should > >> be fixed asap. > >> It seems the error occurs while handling a fault. > >> Could you try to put the ODE log level to debug and see if there is any > >> error ? > >> I guess the incoming message is not exactly the one expected. > >> > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/CXF-to-BPEL-tp15499345s12049p15607287.html > >> > >> > >> Sent from the ServiceMix - User mailing list archive at Nabble.com. > >> > >> > > > > > > > > -- > > Cheers, > > Guillaume Nodet > > ------------------------ > > Blog: http://gnodet.blogspot.com/ > > > > > > -- > View this message in context: > http://www.nabble.com/CXF-to-BPEL-tp15499345s12049p15629439.html > > > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/
