Thx ky, though it's probably not the most elegant solution - right now i don't really see any other. Actually that's more or less what i'm doing right now - i'm hardcoding the path dependent on the url- base(localhost or server).
> Hmm, my approach isn't ideal, but I check for the existence of > folders. > > For example, on my server I know the path /home/user/myname/ > public_html/moduleName is a folder that exists. Likewise, on my > hosted setup, the path C:\Documents and Settings\myname\My Documents > \workspace\projectName exists. > > I hardcode these two locations into my server code, and when it loads > I check for both. If one (and only one) exists, then I set my root > variable (a String) accordingly. You can definitely get the public > folder's location from this, but I don't have the code at hand. > > On Sep 4, 11:39 pm, "alex.d" <[EMAIL PROTECTED]> wrote: > > > >try > > > >GWT.getModuleBaseURL() > > > I'm of course speeking about server-side - on the client side, you > > can't really read files > > > > Server-side? getResourceAsStream maybe? > > > Still need the path, right? > > > >(and include your ...public package in your JAR) > > > That actually may help. But then i'll have it twice - once as a folder > > for html-pages and once as a part of a JAR. May actually work, but not > > an elegant solution ;-) > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
