[ http://jira.jboss.com/jira/browse/JBREM-61?page=comments#action_12315220 ] Tom Elrod commented on JBREM-61: ---------------------------------
Have changed from AccessException to java.rmi.RemoteException. Don't see any need to make this conditional, as is doing this only within UnifiedInvokerProxy, which is specific to EJB call processing. Remoting will remain unaffected. > Possible RMI exception semantic regression > ------------------------------------------ > > Key: JBREM-61 > URL: http://jira.jboss.com/jira/browse/JBREM-61 > Project: JBoss Remoting > Type: Bug > Components: transport > Reporter: Scott M Stark > Assignee: Tom Elrod > Fix For: 1.0.1 final > > > The org.jboss.test.security.test.EJBSpecUnitTestCase.testDeepRunAs method is > currently failing in head after the switch of the default invoker to the > remoting based unified invoker due to a subtle difference in how exceptions > are handled by the jrmp invoker. The test is expecting that the > java.rmi.AccessException thrown by the ejb contaner be wrapped in a > java.rmi.ServerException. This is a wrapping exception used by the jrmp > implementation. The java.rmi.ServerException javadoc: > A ServerException is thrown as a result of a remote method invocation when a > RemoteException is thrown while processing the invocation on the server, > either while unmarshalling the arguments, executing the remote method itself, > or marshalling the return value. A ServerException instance contains the > original RemoteException that occurred as its cause. > The unified invoker is simply throwing back the java.rmi.AccessException. > Although this looks like what the JRMPInvoker is doing, this ignores the fact > that the jrmp implementation sits between the network and the client. We > probably need a strictRMIException mode that allows for the same behavior. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
