I am trying yo connect to a SSB using a remote client. However I may not have the correct classes on this client that this bean returns. This obviously gives me an RMI ClassNotFoundException.
To get around this I was hoping to use something like the remote classloading features of JBoss Remoting. I was hoping that this would involve modifications to the client and allowing the server to still expose the stateless bean for access over RMI.
From what I have read this does not appear to be the case. Can anyone who has used Remoting confirm this for me or am I looking at this the wrong way. By the way I am using Jboss 4.3.
Thanks in advance,
You should just need your interfaces on the client side, and some basic client libs that you can find in the JBOSS_HOME/client directory, you do not need every jar in that directory, just the ejb ones.
You also need a jndi.properties file on the client side.
EJB SSB are for remote method calling, you should not need to go beyond the spec. If you are not familiar with EJBs, I recommend doing a Google search.
Thanks for your reply. I should have made myself clearer.
I am returning a serializable class from the SSB but due to the nature of the project, I may not have this class definition on the client (thus causing an RMI error).
I am familiar with EJBs but am not familiar with JBoss Remoting.
My question is if it will offer the ability to "remotely classload" the server side class without having to make significant changes to the server?
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com