1 Reply Latest reply on May 21, 2013 4:52 AM by jaikiran pai

    Ejb proxy mechanism in Jboss 7.1.1

    Jay Kris Newbie

      Hello there,


      We are doing a migration from Jboss 5.1 to Jboss 7.1.1 , which will be eventually deployed to EAP 6.x.x. 

      Most part of migration went fine. 


      EJB  2.1 is deployed, using the full profile of AS.


      But we are facing a problem now in one peculiar scenario, where the returned object reference's constructer, another EJB is looked up.


      1 Swing client does a look up of a Session bean, it gets the reference. It invokes the business method.

      2 Business method returns an instance of ClientProxy. Class is something like this


      Class ClientProxy implements iProxy {


      ClientProxy() {


      //there is look up of another SessionBean, using the utility classes available only in the server.





      3 . But in the client, there is InvalidClass Exception, and ClassNotFoundException ( for the EJB lookup classes).  

      In Jboss 5.1 , this scenario worked, a Proxy of the instance which was created in the Server ,  was received by the client successfully.


      But in Jboss7.1.1, it seems the returned Object's constructor is again executed at the Client side. 


      Has there any change in the proxying mechanism in 7.1.1  ? 


      Any insights would be helpful.