No it has no "caused by" nor "nest exception".
The rest of error was some list of application calling tree.
I am creating som JINI service accessing the persistence layer. The way JINI services access class is particular, it use a class loader.
I had first many errors, because it did'nt find the class. And with these errors I had a "caused by" message.
With the help of these messages I progress untill now : no more caused by.
And the class maks as unknown is in the classpath. (in fact in the jar of the appli).
Thank's for your help.
It is late here in cyprus now. We will see tomorrow.
Andre
Antonio Gallardo wrote:
Can you send the full stack trace?
Maybe you miss a "caused by" or a "nested exception".
Best Regards,
Antonio Gallardo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
