-
1. Re: Remote SLSB issue
wdfink Nov 29, 2011 1:31 PM (in response to asheffey)Do you use a configuration file of the 4.x server in AS6?
Or you might have a classlosder issue on client side by mixing client jars of 4.x and 6.x version.
-
2. Re: Remote SLSB issue
asheffey Nov 29, 2011 2:11 PM (in response to wdfink)The SLSB is remote, so there is no local configuration besides what's in the Spring config, and there are no 4.x client JARs.
What appears to be the issue is that the Naming configuration which worked in 4.x is not working in 6.x because org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy was removed from 6.x (see https://issues.jboss.org/browse/JBAS-7563).
What values should I use for java.naming.factory.initial and java.naming.factory.url.pkgs to avoid the above exception? Or is there a workaround?
-
3. Re: Remote SLSB issue
huasonator Aug 26, 2012 8:38 PM (in response to asheffey)I have the same problem... Any Idea?
-
4. Re: Remote SLSB issue
wdfink Aug 27, 2012 1:59 AM (in response to huasonator)You have to add the JBoss4 client libraries and set a classloader repository to exclude the JBoss6 classes.
See this wiki
-
5. Re: Remote SLSB issue
huasonator Aug 27, 2012 6:23 PM (in response to wdfink)Yes, I did that, i put the JBoss4 client libraries and works fine... but really is the best way...? why removed the JRMPInvokerProxy? exits a new alternative in AS6 for the lookup classes?
-
6. Re: Remote SLSB issue
wdfink Aug 28, 2012 3:58 AM (in response to huasonator)Yes, that is the best alternative in AS6 I suppose.
I don't know whether the JRMPInvoker is removed. But I think that AS7 is a better alternative because you will have no support for AS6. AS4 and AS5 will still have active members as there are used often.
But the future will be AS7 and here the behaviour is complete different because the EJB invocation is new from client perspective.