[jboss-jira] [JBoss JIRA] Commented: (JBAS-3863) Need to properly test the PooledInvoker for scoped invocations

[ http://jira.jboss.com/jira/browse/JBAS-3863?page=comments#action_12349544 ] Tom Elrod commented on JBAS-3863: ---------------------------------- Have created testsuite tests for scoped deployments using pooled invoker. These tests are found under the testsuite/src/main/org/jboss/test/scoped directory and contains a readme.txt file which includes the following: This test is for JBAS-3198. The bug that is being tested for is when using two scoped ejb deployments and the pooled invoker, the OptimizedObjectInputStream was caching the class definitions when loaded in a static cache without regard to which classloader the class was originally loaded from. Therefore, if ejbA made a call and loaded class Foo (with serialVersionUID = 1L) and then ejbB tried to load class Foo (which would have a serialVerionUID = 2L), the first Foo class loaded (i.e. serialVersionUID = 1L) would be retreived from the cache and used instead of loading the correct class. For the tests themselves, have created two ejb deployments, A and B, which are both scoped deployments. Both return SimpleResponseDTO. The test clients (ScopedUnitTestCase and ScopedBUnitTestCase) use javassist to create a new copy of the SimpleResponseDTO class (one with serialiVersionUID = 1L and the other with serialVersionUID = 2L) that gets included its ejb deployment and on local classpath (for the client). To properly test, have to run both ScopedUnitTestCase and then ScopedBUnitTestCase (or vise versa) against same running instance of JBoss server (i.e. running one, then re-booting JBossAS and running the other does not test for this bug fix). -- 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 - For more information on JIRA, see: http://www.atlassian.com/software/jira