Hi JBI Joe, Ode understand three kinds of message formats coming from the JBI bus:
1) Normalized Messages (per the JBI spec) 2) "Wrapped" WSDL 1.1 normalized messages (per JBI spec) 3) SOAP messages where the Body has been copied verbatim into the JBI message content You'll get MessageTranslationExceptions everytime you try to interoperate with another component that doesn't follow these rules. Many so-called "lightweight components" offered by ServiceMix use different message representations, so you have two choices to make this work: 1) Use a mediating JBI component in-between (e.g. XSL) 2) Write a custom Mapper (org.apache.ode.jbi.msgmap.Mapper) I'd be happy to work with you on creating a working example. Can you provide the use-case? Maybe something like a few Java components/endpoints and the sketch of a BPEL to orchestrate them? I could take it from there... cheers, alex On 7/12/07, jbi joe <[EMAIL PROTECTED]> wrote:
I got a MessageTranslationException; Could not find mapper for request message for JBI MEX -blahblahblahblah is failed. Looking at the list here I see that others have also had to deal with this exception. Maybe some additional examples, with some valid messages that span ODE JBI, etc.. are in order. SO How do I fix it? Other posts have given me some clues that perhaps my wsdl and msg format are incorrect. The ODE examples that are provided work fine. However, I have some BPEL reaching out to invoke some NMR endpoints on my servicemix ESB. I dont see any examples that show this. Perhaps a sample that has java kicking off a BPEL endpoint, then the BPEL kicking of a bunch of java based endpoints. I know its all supposed to be abstract, but Im from missouri, show me,,, please.. TIA ANy help greatly appreciated.. TIA -- View this message in context: http://www.nabble.com/Could-not-find-a-mapper-for-request-message-tf4067593.html#a11558251 Sent from the Apache Ode User mailing list archive at Nabble.com.
