On Tue, Jan 26, 2010 at 6:21 AM, m.mil...@newelements.de < m.mil...@newelements.de> wrote:
> No, i definetly mean not the XYZ.nochache.js. > > Here is a line from my firebug: > http://localhost:8080/application/64CE9F3B21EDFDB2ADBA49308C361972.cache.js > > this is what gwt tries to load, but the file is definetly reachable > under this path: > > http://localhost:8080/application/application/64CE9F3B21EDFDB2ADBA49308C361972.cache.js > > Are you trying to run this under an external app server (e.g. Tomcat), or have you simply changed the port that the embedded server uses? If you're deploying your app to an external app server, I can see how you might end up with an "application/application" path (although I don't know how correct it would be). Let's take a step back, can you describe the directory structure that you see after you run the GWT compiler? > i think the gwt compiler has a problem with it´s pathes and the > folders within the war file. > i have a new problem, when i compile the application and start it at > the application server all pathes to the images folder are wrong, but > this time the name of the application instance is missing in the image > pathes. > > i´m absolutely sure both problems had nothing to do with the upgrade > but are compiler errors. i had similar problems before when ich made > an if statement on an Tree. > > my original code was something like: > if ( tree != null ) > > that caused compiler error that have not been displayed but the > XYZ.cache.js couldn´t been found > > wehn ich changed the line to: > if ( tree.getRoot() != null ) > > the compiled code worked. > I was able to successfully run the following code in both Development and Web mode: public class Test implements EntryPoint { public void onModuleLoad() { Tree t = new Tree(); TreeItem ti = null; if (ti != null) { } else { ti = new TreeItem("hello there"); } t.addItem(ti); RootPanel.get().add(t); } } Is there something different between your app and the above snippet? So i guess, you google folks have to do a coulpe of fixes to your > compiler :-) > I think several, mutually exclusive issues are being confused here. Would you mind sending me your project, or a sample project that reproduces the issues you mention above? > On 11 Jan., 20:37, Chris Ramsdale <cramsd...@google.com> wrote: > > I second Rajeev's comments, there are a couple of oddities that you may > > experience when upgrading. > > > > That said, I'm wondering about the following (@m.militz): > > > > 1. I'm assuming you meant XYZ.nocache.js and not XYZ.cache.js. Is this > > correct? > > 2. While GWT does produce a .html when you create a new project, it does > not > > create this file every time, and it does not alter it once created. Put > > another way, I don't believe that GWT is mucking with your Project.html > file > > (not even during upgarde). Is your script tag, within Project.html, > > incorrect for some reason? What happens if you simply change it to > reference > > <module>/<module>.nocache.js? > > > > - Chris > > > > On Mon, Jan 11, 2010 at 12:33 PM, Rajeev Dayal <rda...@google.com> > wrote: > > > Hi, > > > > > Have you seen an instance where GWT tries to load the nocache.js file > > > directly from the root of your war folder? What does the HTTP GET > request > > > look like? > > > > > There is definitely a bug in GWT when switching between SDKs. The > problem > > > is twofold: > > > > > 1) The hosted.html file does not get regenerated. The workaround for > this > > > is to blow away the generated subdirectories of the war directory after > > > switching SDKs. > > > 2) Because of the caching rules that GWT's embedded Jetty uses, > hosted.html > > > is not re-requested by the browser whenever it is requested. The > workaround > > > for this is to clear your browser's cache. > > > > > Rajeev > > > > > On Mon, Jan 11, 2010 at 11:16 AM, m.mil...@newelements.de < > > > m.mil...@newelements.de> wrote: > > > > >> Thanks for the hints, but all of this issues i could handle by myself. > > >> the problem is gwt produces erroneus code. it tries loading > > >> XYZ.cache.js files from the war folder, but into the war fiolder are > > >> subdirectories where the js files lies. > > >> It looks like this only happens on special occasions but i still can´t > > >> fire out what is responsible for that. > > > > >> On 9 Jan., 23:15, Sorinel C <scristescu...@hotmail.com> wrote: > > >> > Hi all, > > > > >> > There small tricks related with the environment, which aren't > > >> > documented, in the GWT tutorial. > > > > >> > Here you can find what helped me to solve the migration issues: > > > > >> > > http://ui-programming.blogspot.com/2009/12/update-your-application-to. > > >> .. > > > > >> > Cheers! > > > > >> -- > > >> You received this message because you are subscribed to the Google > Groups > > >> "Google Web Toolkit" group. > > >> To post to this group, send email to > google-web-tool...@googlegroups.com. > > >> To unsubscribe from this group, send email to > > >> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > <google-web-toolkit%2bunsubscr...@googlegroups.com<google-web-toolkit%252bunsubscr...@googlegroups.com> > > > > >> . > > >> For more options, visit this group at > > >>http://groups.google.com/group/google-web-toolkit?hl=en. > > > > > -- > > > You received this message because you are subscribed to the Google > Groups > > > "Google Web Toolkit" group. > > > To post to this group, send email to > google-web-tool...@googlegroups.com. > > > To unsubscribe from this group, send email to > > > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > <google-web-toolkit%2bunsubscr...@googlegroups.com<google-web-toolkit%252bunsubscr...@googlegroups.com> > > > > > . > > > For more options, visit this group at > > >http://groups.google.com/group/google-web-toolkit?hl=en. > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
