Camilo Arango wrote: > Not always. I seems that only exceptions thrown by the called object > are propagated by the client. In my case, the exception is thrown by a > filter, and therefore the call to the Spring remoting proxy never > occurs and I get and ugly 500 response code at the client. > > What would be the best thing to do in that case?
Depends where ExceptionTranslationFilter appears in your chain. Which filter is throwing the exception, and where is ETF in your chain? Cheers Ben ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Home: http://acegisecurity.org Acegisecurity-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/acegisecurity-developer
