1 2 Previous Next 17 Replies Latest reply on Jan 21, 2009 9:21 AM by bortx Go to original post
      • 15. Re: Jarjared version of JBC3 for using in JBossAS 4.2
        jorgemoralespou_2

        We are using tagged release 3.0.2.CR2.

        In those lines is:

         RPCManager barfingRpcManager = EasyMock.createNiceMock(RPCManager.class);
         RPCManager originalRpcManager = cache1.getConfiguration().getRuntimeConfig().getRPCManager();
        


        Is there a way to validate the refactorings, only passing a subset of tests that do not use that reflecting code?
        Supposedly, even using reflection it should work, because it should use reflective methods on the refactored code. But not sure at all.

        Will keep trying as it is very important to us to upgrade our caches to a newer version, but don't want to use classloading isolation in apps due to shared classes between apps.

        • 16. Re: Jarjared version of JBC3 for using in JBossAS 4.2
          manik

          The first one would be a mock, as expected, and the second should be the actual RPC manager. I can't imagine how you would get proxies for the second instance, even if you are using jarjar'ed code. Could you paste the FQCN of the class you get for 'originalRpcManager' ?

          • 17. Re: Jarjared version of JBC3 for using in JBossAS 4.2

            For both classes (originalRpcManager and rpcManager) we get a dynamic easy mock proxy instance of the same type: $Proxy20

            The toString yields:
            EasyMock for interface som.org.jboss.cache.RPCManager

            I hope this can help,

            Thanks,

            1 2 Previous Next