On Tue, Oct 21, 2008 at 7:05 AM, salvatore cospito <[EMAIL PROTECTED]> wrote: > P.S Paul i've read the documentation , that kind of answer is not required > ;-)
I think you'll find you get fewer answers like that if you take the time to ask better questions. Subjects that don't summarize the email often get skipped by knowlegeable people because they're busy with other things and don't have time to figure out whether or not they can answer your question. Also, this might just be a personal thing but, I find multiple exclamation points blindingly rude--the fact that you've posted a question to the mailing list implies that you're looking for help so stuff like "please help me!!!!!!!!!!!!" makes me choose not to reply. If you look here: http://www.catb.org/~esr/faqs/smart-questions.html you may come to understand why it would have helped your cause to say something like "I've read the documentation and searched the mailing list but I can't figure out how to launch a GWT client app from a regular Java main method. Is it possible? Where can I look?" in your first message. At the very least, Paul's answer would not have happened. While I'm here, I'll try to be useful. I doubt you'll be able to do what you're looking to do without just running some part of the GWT library. As obesga said, GWT client code is intended to run either in hosted mode (which emulates a browser) or as compiled output in a full-blown web browser. Depending on how you've modularized your code, it may be possible to share some code between a GWT app and a regular Java app, but there's lots of stuff you have to consider if you decide to try that. As your exception message describes, GWT.create only works inside a GWT client application so you can't call it and you can't call anything that calls it. Also, anything implemented in JSNI (or anything that calls something that's implemented in JSNI) is not going to work in regular Java. Finally, you probably don't want to rely on anything in the com.google namespace that is GWT-specific. (The last point is mostly a way to stay out of trouble with the first two points, but it's also a matter of preferring JRE classes over GWT classes when there's one in each that does the same thing.) Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
