nocache.js Resource not found
maku
I'm a gwt newbie and I'm playing around with gwt for evaluation
purposes.
After some successfully trials I tried to use a RPC.
But now, when I try to start the app in Eclipse I get an error
"Resource not found: at.testapp.Application.nocache.js"
and the app isn't starting.
I've no idea where the request come from.
Could anybody give me a hint?
TIA
Martin
Dan Morrill
Hi, Martin!
Which version of GWT are you using? The "nocache.js" bootstrap model is a new feature that will be in the upcoming 1.4 version. If you are using the current released version -- 1.3.3 -- then you need to use gwt.js rather than the nocache.js version.
Are you using 1.3.3?
- Dan Morrill
maku
I use version 1.3.3.
It seems that the problem only occurrs when I start the app with
com.google.gwt.dev.GWTShell. When I make a war-File and use this I get
no error.
Martin
On 16 Mai, 16:51, "Dan Morrill" <morri...@google.com> wrote:
> Hi, Martin!
>
> Which version of GWT are you using? The "nocache.js" bootstrap model is a
> new feature that will be in the upcoming 1.4 version. If you are using the
> current released version -- 1.3.3 -- then you need to use gwt.js rather than
> the nocache.js version.
>
> Are you using 1.3.3?
>
> - Dan Morrill
>
Dan Morrill
Hi again, Martin!
If you are using version 1.3.3, then your host HTML page should not be referring to "at.testapp.Application.nocache.js" at all. There is no such file in the 1.3.3 release; that error that the hosted mode servlet is reporting is essentially a "404 - Not Found" error.
For a 1.3.3 application, you need to use a <meta name="gwt:module" content="at.testapp.Application"> tag along with a <script src="gwt.js"> tag, similar to the example shown here:
http://code.google.com/webtoolkit/documentation/com.google.gwt.doc.DeveloperGuide.Fundamentals.HostPage.html
Does your host HTML page have those tags set correctly?
- Dan
maku
here is my html page.
<html>
<head>
<title>Testapp</title>
<meta name='gwt:module' content='at.testapp.Application'>
</head>
<body>
<script language="javascript" src="gwt.js"></script>
<iframe id="__gwt_historyFrame" style="width:0;height:0;border:0"></
iframe>
</body>
</html>
I'm sure that I've no ref to "nocache.js" in my app. (I did a full
text search on the directory)
BTW, I was able to start the app before I implemented the code for my
testRPC. No idea what's going on now.
Maybe it's better to start a new project and insert the code step by
step.
Martin
On 16 Mai, 17:14, "Dan Morrill" <morri...@google.com> wrote:
> Hi again, Martin!
>
> If you are using version 1.3.3, then your host HTML page should not be
> referring to "at.testapp.Application.nocache.js" at all. There is no such
> file in the 1.3.3 release; that error that the hosted mode servlet is
> reporting is essentially a "404 - Not Found" error.
>
> For a 1.3.3 application, you need to use a <meta name="gwt:module" content="
> at.testapp.Application"> tag along with a <script src="gwt.js"> tag, similar
> to the example shown here:http://code.google.com/webtoolkit/documentation/com.google.gwt.doc.De...
>
> Does your host HTML page have those tags set correctly?
>
> - Dan
>
Jason Essington
build at one point, then went back to 1.3.3?
try deleting your www/ folder and recompiling and rebuilding your war
files.
Basically, it sounds like you have a cached version of gwt.js from a
1.4 build.
-jason
Manuel Darveau
The problem occured after I tried 1.4 and the switched back to 1.3.3...
Hope it help!
Manuel
On 5/16/07, maku <marti...@gmx.at> wrote:
>
Adrian
care to admit. I too had had a look at 1.4 and then gone back to 1.3.
In my case, the version of gwt.js from 1.4 had been cached (in hosted
mode!). Here's what worked for me:
- start in hosted mode and get the error
- change the Module.html bit of the URL to gwt.js to view this file
- you'll probably see a shortish file (20-30 lines) which is the 1.4
version
- press the refresh button and you should see a different longer file
- off you go!
Very frustrating. Who'd have even thought the hosted browser would be
caching files? Oh well, fixed now. Onwards.
maku
the clearing the cache solved the problem.
Thanks for helping.
Regards,
Martin
On 16 Mai, 19:35, "Manuel Darveau" <manueldarv...@gmail.com> wrote:
> I had the same problem and clearing the cache in IE solved the problem...
> The problem occured after I tried 1.4 and the switched back to 1.3.3...
>
> Hope it help!
>
> Manuel
>
> > > > > thenocache.js version.
Ed Coyne
Also you can just do ctl+f5 to force a refresh so you dont have to
open up IE to clear the cache.
Ed
On May 16, 1:35 pm, "Manuel Darveau" <manueldarv...@gmail.com> wrote:
> I had the same problem and clearing the cache in IE solved the problem...
> The problem occured after I tried 1.4 and the switched back to 1.3.3...
>
> Hope it help!
>
> Manuel
>