I tried to change existing code to not throw the exception but to set the error on the exchange being routed but as I expected an IllegalStateException is thrown since SecuredBroker is not the owner of the message exchange.
Do you know how it can be handled? Piotr On 7/12/07, Thomas Termin <[EMAIL PROTECTED]> wrote:
Sounds like a good idea for me. Piotr Bzdyl wrote: > Hi, > > I am trying to use SecuredBroker but I have one problem with its > current implementation. If the user is not authorized to send the > exchange do the endpoint, then the SecurityException is thrown and the > exchange is not sent back to the calling component. This is the cause > that the caller won't get any response. > > Shouldn't it return the exchange to the caller with status set to > ERROR and the security exception set as an error on the message > exchange? > > Thanks and regards, > Piotr > -- Thomas Termin _______________________________ blue elephant systems GmbH Wollgrasweg 49 D-70599 Stuttgart Tel : (+49) 0711 - 45 10 17 676 Fax : (+49) 0711 - 45 10 17 573 WWW : http://www.blue-elephant-systems.com Email : [EMAIL PROTECTED] blue elephant systems GmbH Firmensitz : Wollgrasweg 49, D-70599 Stuttgart Registergericht : Amtsgericht Stuttgart, HRB 24106 GeschÀftsfÌhrer : Holger Dietrich, Thomas Gentsch, Joachim Hoernle