Exceptions in Axis stack not reported to client
-----------------------------------------------
Key: SANDESHA2-130
URL: https://issues.apache.org/jira/browse/SANDESHA2-130
Project: Sandesha2
Issue Type: Bug
Affects Versions: 1.3
Environment: Axis2/Rampart/Sandesha2 v 1.3
Reporter: Hans G Knudsen
Hi!
If errors occurs in the Axis stack after Sandesha has taken over handling - the
exception is not handed back to the calling client.
Eg. if an error occur in Rampart trying to do the outgoing security handling.
Testcase:
- misspell
<ramp:passwordCallbackClass>wrong.class.Name</ramp:passwordCallbackClass>
Sandesha does not recognize the error situation - and continues according to
sending policy. And the session times out with the following error :
Sandesha2 could not send the message on sequence <URL> as the sequence has
timed out.
I have only had time to test on version 1.3.
/hans
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]