yeah, Toplink is supposed to run in Tomcat so in theory it should work. If you google:
"toplink Internal Exception: java.lang.ClassNotFoundException:" there seem to be a lot of people who have had the same exception as you, but for a variety of different reasons. I'm sorry I don't know anything about Toplink, I hope somebody else does, but what I would do is this: First I would prove that the problem is not with my own GWT code set up by writing a simple RPC service that simply instantiated a new com.app.server.Person object and returned it to the client. That would prove the class is within classpath as far as GWT RPC is concerned. Second I would take a guess that the root cause of the problem lies in the way Toplink handles multiple applications, in particular how it allocates classloaders. It is possible that the way you have set it up, it has created a separate classloader for handling your persistent objects, therefore your classes which Tomcat will have loaded in your GWT app classloader courtesy of GWT's hosted mode Tomcat deployment may not be visible to it. This is just a guess, but if it was near the mark, if you trawl through the results of aforementioned google search, you may find the answer is to either override default Toplink behaviour to stop it making a new classloaders for itself, or maybe you need to configure it to obtain your GWT applications classloader and include it /use it somehow. Each classloader has its own classpath. sorry I can't be of more help regards grergor On Nov 11, 2:29 pm, darkAngel <[EMAIL PROTECTED]> wrote: > Any suggestions ??? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
