Forwarding properties between BC-SOAP and SE-EIP

View: New views
2 Messages — Rating Filter:   Alert me  

Forwarding properties between BC-SOAP and SE-EIP

by Khanh Maudoux :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I am proxying a WebService with PEtALS and I would like to modify my SOAP message.
To do that, I am using a SE EIP in mode routing-slip and a SE custom.
However, it seems that the SE EIP does not transmit properties (where my SOAP's header is) from my BC-SOAP (in mode consume):
My SOAP Client use WS-Addressing but properties are lost in the SE EIP.
When I do not use the SE EIP, there is no problem and my SOAP Header is OK.

If I understood, my SOAP's Header is stored in the exchange's properties but in SE EIP, the exchange's properties are not forwarded so they are lost.
It seems that the SE EIP works only on the attributes inNormalizedExchange of the object exchange but properties are only stored in the object exchange (RoutingSlip.process) so the method PatternHelper.copy can not get my SOAP's header.

Do you agree with my analysis and is it a bug or did I misunderstood?

Best regards,

Khanh Tuong Maudoux


Re: Forwarding properties between BC-SOAP and SE-EIP

by Roland Naudin - EBM WebSourcing :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

hi Khan,

You are right, the EIP didn't relay the Properties.
The up to come version will.

Regards,
/Roland

Le mardi 17 juin 2008 à 08:29 -0700, Khanh Maudoux a écrit :

> Hi,
>
> I am proxying a WebService with PEtALS and I would like to modify my SOAP
> message.
> To do that, I am using a SE EIP in mode routing-slip and a SE custom.
> However, it seems that the SE EIP does not transmit properties (where my
> SOAP's header is) from my BC-SOAP (in mode consume):
> My SOAP Client use WS-Addressing but properties are lost in the SE EIP.
> When I do not use the SE EIP, there is no problem and my SOAP Header is OK.
>
> If I understood, my SOAP's Header is stored in the exchange's properties but
> in SE EIP, the exchange's properties are not forwarded so they are lost.
> It seems that the SE EIP works only on the attributes inNormalizedExchange
> of the object exchange but properties are only stored in the object exchange
> (RoutingSlip.process) so the method PatternHelper.copy can not get my SOAP's
> header.
>
> Do you agree with my analysis and is it a bug or did I misunderstood?
>
> Best regards,
>
> Khanh Tuong Maudoux
>
>
> pièce jointe document plein texte (message-footer.txt)
> --
> You receive this message as a subscriber of the petals-users@... mailing list.
> To unsubscribe: mailto:petals-users-unsubscribe@...
> For general help: mailto:sympa@...?subject=help
> OW2 mailing lists service home page: http://www.ow2.org/wws
--
Roland NAUDIN
PEtALS Team

EBM Websourcing
05 34 32 03 13

Try PEtALS at
http://petals.objectweb.org




--
You receive this message as a subscriber of the petals-users@... mailing list.
To unsubscribe: mailto:petals-users-unsubscribe@...
For general help: mailto:sympa@...?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
LightInTheBox - Buy quality products at wholesale price