BC-SOAP and AxisFault

[Khanh Maudoux]

Hi,

I'm actually trying to use a Web Service with the BC-SOAP.
However, I have got an unexpected error : it seems that BC-SOAP does not treat correctly AxisFault.
Indeed, my Web Service responds with an expected Exception which is received by the WSCaller as an AxisFault.
The AxisFault is then transformed into a JBIFault but does not seems to be sent to my Web Service's client.

Do you agree with this analysis (I'm using quickstart-2.1.1 and the revision 8193 for the BC-SOAP) ?

Best regards,

Khanh Tuong Maudoux

[Christophe Hamerling]

As far as I understand, you are proxying a WebService with PEtALS.
Your analysis is good. I have just checked the source code, the JBIFault taken from the message exchange on the consumer side is used to create the SOAP Envelope of the response.
Can you please send all the SOAP messages on server and client side ?

Thanks
Christophe

On Wed, Jun 11, 2008 at 5:34 PM, Khanh Maudoux <kmx.petals@...> wrote:

Hi,

I'm actually trying to use a Web Service with the BC-SOAP.
However, I have got an unexpected error : it seems that BC-SOAP does not
treat correctly AxisFault.
Indeed, my Web Service responds with an expected Exception which is received
by the WSCaller as an AxisFault.
The AxisFault is then transformed into a JBIFault but does not seems to be
sent to my Web Service's client.

Do you agree with this analysis (I'm using quickstart-2.1.1 and the revision
8193 for the BC-SOAP) ?

Best regards,

Khanh Tuong Maudoux


--
View this message in context: http://www.nabble.com/BC-SOAP-and-AxisFault-tp17780690p17780690.html
Sent from the Petals Users mailing list archive at Nabble.com.



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

--
Christophe Hamerling
PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
http://petals.ow2.org
http://petals.ebmwebsourcing.com
Phone : [phone]
Skype : christophe.hamerling

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

[Khanh Maudoux]

Hi Christophe,

Thanks for your response!
Indeed, I am proxying a WebService with PEtALS but I use a SE EIP too and a custom SE which aims to transform the message.
If you say that the BC-Soap in consume mode read the JBIFault, it is ok (I just test it and it works) but what about the SE EIP (in routing-slip mode)?

In the SE-EIP, the method PatternHelper.processSentExchange() get the JBIfault but does not set it in the exchange. Moreover, the message is not sent.

I test it and the error seems to be there.

Doesn't the code should be like that (but I do not know the consequence)?

    public static NormalizedMessage processSentExchange(Exchange sentExchange,
            Exchange originalExchange, ExchangeContext context) throws JBIException {
        ...
            if (sentExchange.getFault() != null) {
                context.getLogger().fine("a fault is returned, set it on the original Exchange.");
                // fault on piped exchange, set it on the original exchange
                // do not return a message
                Fault fault = originalExchange.createFault();
                fault.setContent(sentExchange.getFault().getContent());

                originalExchange.setFault(fault);  //NEW : to put the fault in the response
                receivedMessage = sentExchange.getOutMessage();   //NEW : to send the message
            } else {
      ...



Best regards,

Khanh Tuong Maudoux

[Christophe Hamerling]

We need to check this.
Thanks !

On Thu, Jun 12, 2008 at 12:56 PM, Khanh Maudoux <kmx.petals@...> wrote:

Hi Christophe,

Thanks for your response!
Indeed, I am proxying a WebService with PEtALS but I use a SE EIP too and a
custom SE which aims to transform the message.
If you say that the BC-Soap in consume mode read the JBIFault, it is ok (I
just test it and it works) but what about the SE EIP (in routing-slip mode)?

In the SE-EIP, the method PatternHelper.processSentExchange() get the
JBIfault but does not set it in the exchange. Moreover, the message is not
sent.

I test it and the error seems to be there.

Doesn't the code should be like that (but I do not know the consequence)?

   public static NormalizedMessage processSentExchange(Exchange
sentExchange,
           Exchange originalExchange, ExchangeContext context) throws
JBIException {
       ...
           if (sentExchange.getFault() != null) {
               context.getLogger().fine("a fault is returned, set it on the
original Exchange.");
               // fault on piped exchange, set it on the original exchange
               // do not return a message
               Fault fault = originalExchange.createFault();
               fault.setContent(sentExchange.getFault().getContent());

               originalExchange.setFault(fault);  //NEW : to put the fault
in the response
               receivedMessage = sentExchange.getOutMessage();   //NEW : to
send the message
           } else {
     ...

Best regards,

Khanh Tuong Maudoux




--

View this message in context: http://www.nabble.com/BC-SOAP-and-AxisFault-tp17780690p17797255.html

Sent from the Petals Users mailing list archive at Nabble.com.

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

--
Christophe Hamerling
PEtALS ESB Research Engineer / Product Manager @ eBM WebSourcing
http://petals.ow2.org
http://petals.ebmwebsourcing.com
Phone : [phone]
Skype : christophe.hamerling

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