ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thilina Gunarathne" <cset...@gmail.com>
Subject Re: Using SOAP Headers in BPEL
Date Wed, 21 Nov 2007 16:40:13 GMT
Hi Alex,
Thanks a lot for the reply... Actually changing the WSDL's to reflect
our custom header is possible for us. Anyway we are trying hard to
make our WSDL's more descriptive :).. AFAIK even Axis2 code generation
supports headers defined in WSDL.

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..


On Nov 21, 2007 11:08 AM, Alex Boisvert <boisvert@intalio.com> wrote:
> On 11/21/07, Thilina Gunarathne <csethil@gmail.com> wrote:
> >
> > I also need to make sure that the resulting BPEL is standard and
> > portable.  My question is whether the second mechanism is a standard
> > way and whether it is supported by other BPEL engines..
> SOAP header mapping is completely standard, and perhaps equally important,
> it can be different on the client and the server without impact to
> interoperability.  This means you might get a WSDL that doesn't define any
> headers, or defines headers but doesn't map them into message parts, and you
> can add/change the mappings without changing the transport-level messages.
> I don't know if it's supported by other engines but I've seen a good number
> of WSDLs in the wild that use this approach.
> cheers,
> alex

Thilina Gunarathne  - http://thilinag.blogspot.com

View raw message