Thanks for the prompt answer, but
1) yes, the client has everything it needs on its path
2) the problem doesn't not appear when the first call to the EJB is a call
that returns the result of Document.parse(). As long as that first
call is made, the client is quite happy to unmarshal anything I throw
at it. Actually, as a temporary fix I have decided to include a dummy
call to getDocument(0) in my application just to make the remaining
code work.
This (imho) proves that the code and the client are fine, but a subtle
difference in the Document created from scratch means that a
different Class is loaded and causes every call that follow to fail.
Now I don't know much about class loading and likes, so I can't
really figure it out.
Cheers
Franck
"Downey, Tim" <[EMAIL PROTECTED]> on 05/07/2001 14:50:43
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: org.w3c.Document RMI serialization
Franck,
Does the client side program have xerces in its classpath? If the client
didn't have xerces in the classpath, it would be unable to unmarshal the
Document class.
Good luck,
-tim
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
