You are using the old version of the HomeProxy class in your client but the
server has the newer one

marc


|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of David
|Jencks
|Sent: Saturday, May 19, 2001 8:47 AM
|To: [EMAIL PROTECTED]
|Subject: Re: [JBoss-dev] current source - classloading & jndi?
|
|
|Hi,
|I had a similar problem, prompting me to suggest a different
|directory/build structure for jboss, with less duplication. No one has
|responded with even a comment, however.
|
|What I did was grep the sources to find which class has the VersionUID,
|look in the build.xml to find out what jar it ends up in, and replace all
|instances of that jar with the new one. I'm not sure, but I think its
|jboss-client.jar
|BTW, I think the stack trace should be in your log file.
|
|Hope this helps
|david jencks
|
|On 2001.05.19 04:01:09 -0400 "Ferguson, Doug" wrote:
|> When I deploy to jboss that is built from the current source I get the
|> following stack trace on my jndi lookup....
|>
|> javax.naming.CommunicationException
|>  with Root Exception java.io.InvalidClassException:
|>    org.jboss.ejb.plugins.jrmp.interfaces.HomeProxy;
|>    local class not comptible: stream classdesc
|> serialVersionUID=4324...923
|>                                local classdesc
|> serialVersionUID=6136...997
|> at java.io.OjbectStreamClass.validateLocalClass(UnkownSource)
|> ....
|> at java.rmi.MarshalledObject.get(Unknown Source)
|> at org.jnp.interfaces.NamingContext.lookup(NamingContext 299)
|> at org.jnp.interfaces.NamingContext.lookup(NamingContext 279)
|> at javax.naming.InitialContext.lookup(Unknow Source)
|> at amazin.beans.Client.ini(Clien.java 28)
|> at amzain.beans.Client.main(Client.java 22)
|>
|> I retyped this stackTrace cuz I can't cut and paste from this winblows.
|> ok...
|>
|> Client.java 38 is a lookup on the HomeInterface....
|> ((KeyGeneratorHome)
|> context.lookup("KeyGenerator")).create("TheKeyGenerator");
|>
|> The first thing that will come to mind, is oh, you've updated the
|> interface
|> and the client & jboss are out of sync, however jboss2.2.1 works just
|> fine
|> with the same jar...
|>
|> d.
|>
|>
|>
|>
|> _______________________________________________
|> Jboss-development mailing list
|> [EMAIL PROTECTED]
|> http://lists.sourceforge.net/lists/listinfo/jboss-development
|>
|
|
|_______________________________________________
|Jboss-development mailing list
|[EMAIL PROTECTED]
|http://lists.sourceforge.net/lists/listinfo/jboss-development



_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to