Hi Alex, Thanks again... It worked like a charm in the invokes. I had a little issue with receiving the messages, which I got fixed with a little tweak in SOAPMessageConverter... I reported it in the jira ODE-211[1] and attached a trivial patch.. Not sure whether it's the correct solution.. So please review it carefully before committing..
I'll try to submit a test case, so that it won't fail again.. But need to study the ODE test setup before doing that. thanks, Thilina [1] https://issues.apache.org/jira/browse/ODE-211 On Nov 21, 2007 12:10 PM, Alex Boisvert <[EMAIL PROTECTED]> wrote: > On 11/21/07, Thilina Gunarathne <[EMAIL PROTECTED]> wrote: > > > > Just to get it reconfirmed by the experts, I was wondering whether the > > usage of BPEL variables containing two parts (one for header and other > > for body defined in WSDL) and mapping them correctly to the SOAP Body > > and Header in Receive/Invoke is a standard?. I was wondering that > > because I was not able to find a sample that does it... Sorry for > > troubling again.. > > > Yes, it's standard BPEL. In fact, BPEL is only aware of message parts (one > or many); the header mappings are invisible to processes since BPEL works > only at the abstract WSDL level (messages and portTypes). > > alex > -- Thilina Gunarathne - http://thilinag.blogspot.com
