Hi Joseph,
Did you manage to find right jars?
If not could please post your client jar lists so that I can compare those
with mine.
Thanks
Biswojit
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3888065#3888065
Reply to the post :
http://www.jboss.org/ind
I'm experiencing the exact same problem looking up EJB's remotely (from one
JBOSS server to another JBOSS server). What client jars did you include? Thanks.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3887311#3887311
Reply to the post :
http://www.jboss.or
Hi Darranl,
Yes you are right.
Thanks for your help.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886202#3886202
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886202
--
Yes the error looks as if you are using the wrong jars with the client to
access JBoss.
The client needs the jars from JBoss 4.0.2 to access JBoss 4.0.2.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885867#3885867
Reply to the post :
http://www.jboss.org/
Hi darranl,
Thanks for your reply.
Here is the stack trace
javax.naming.CommunicationException [Root exception is
java.io.InvalidClassException: org.jboss.util.id.GUID; local class
incompatible: stream classdesc serialVersionUID = 3289509836244263718, local
class serialVersionUID = 692642194650
Have you made sure that the Swing application is configured to use the jars
from JBoss 4.0.2 instead of the jars from JBoss 3.2.2.
If this is not the problem could you please post the exception (including stack
trace) here.
View the original post :
http://www.jboss.org/index.html?module=bb&op=
