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? Thanks, Camilo Arango > Camilo Arango wrote: > > I am using Acegi fo a 3-tier Eclipse RCP application using HTTP > > remoting. It has come to my attention that when a remote call throws a > > AccessDeniedException, in the client it is translated to a > > RemoteInvocationException. It would be useful to have an > > AccessDeniedException in this cases instead. > > Translation is undertaken by ExceptionTranslationFilter, so just remove > it from your filter chain for URI patterns requested by your web > application. Thus, native exceptions (complete with stack traces etc) > will be serialized and sent to the caller. > > 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
