Report Month

[Matthieu Riou <ma...@gmail.com>]

Hi all,

This month is our report month. I've posted an update here:

http://wiki.apache.org/incubator/December2006

Feel free to modify and complement if I've forgotten something important.

Matthieu

Re: Manipulating the soap header from bpel

[Maciej Szefler <mb...@intalio.com>]

The session token is a bit of a special case. ODE supports the passing
of such tokens using Message exchange properties (see MessageExchange
interface). If you pass in a session identifier using these
properties, it will be associated with the partner link so all future
calls to the partner will have the session identifier. Now how the
session id gets in/out of your message is up to the integration layer.
So you could customize the axis2 integration for examle to look for
your session token in the header and drop it into the approperiate
message exchange property. This is already being done by the Axis
code, except the location of the token is likely not the same as where
you are expecting to find it. This approach has the benefit of not
requiring any changes to wsdl, and you won't need to be manually
copying session ids in the BPEL process.

-maciej


On 12/17/06, Jim Alateras <ji...@comware.com.au> wrote:
> Paul R Brown wrote:
> >
> >
> > Hi, Jim --
> >
> >> Is there anyway to manipulate the SOAP header using the <copy>
> >> construct in BPEL. The specific example is that I need to make a
> >> request to a service to retrieve a 'session token' and in  subsequent
> >> calls to the service I need to embed the 'session token'  into the
> >> soap header.
> >
> >
> > Inside of the BPEL world, there is no SOAP, only WSDL.  So, if that  bit
> > of XML in the SOAP envelope is a WSDL part, you're in business.   If
> > not, you're out of luck.
> >
> okay...so I guess all i need to do is define the binding section
> (i.e. <soap:header>) appropriately and everything should just work.
>
> cheers
> </jima>
>

Re: Manipulating the soap header from bpel

[Jim Alateras <ji...@comware.com.au>]

Paul R Brown wrote:
> 
> 
> Hi, Jim --
> 
>> Is there anyway to manipulate the SOAP header using the <copy>  
>> construct in BPEL. The specific example is that I need to make a  
>> request to a service to retrieve a 'session token' and in  subsequent 
>> calls to the service I need to embed the 'session token'  into the 
>> soap header.
> 
> 
> Inside of the BPEL world, there is no SOAP, only WSDL.  So, if that  bit 
> of XML in the SOAP envelope is a WSDL part, you're in business.   If 
> not, you're out of luck.
> 
okay...so I guess all i need to do is define the binding section
(i.e. <soap:header>) appropriately and everything should just work.

cheers
</jima>

Re: Manipulating the soap header from bpel

[Paul R Brown <pa...@gmail.com>]

Hi, Jim --

> Is there anyway to manipulate the SOAP header using the <copy>  
> construct in BPEL. The specific example is that I need to make a  
> request to a service to retrieve a 'session token' and in  
> subsequent calls to the service I need to embed the 'session token'  
> into the soap header.

Inside of the BPEL world, there is no SOAP, only WSDL.  So, if that  
bit of XML in the SOAP envelope is a WSDL part, you're in business.   
If not, you're out of luck.

-- Paul

Manipulating the soap header from bpel

[Jim Alateras <ji...@comware.com.au>]

Is there anyway to manipulate the SOAP header using the <copy> construct 
in BPEL. The specific example is that I need to make a request to a 
service to retrieve a 'session token' and in subsequent calls to the 
service I need to embed the 'session token' into the soap header.

cheers
</jima>