I can tell you that if you are working in anyway with JSO objects, devmode
will mask out null pointer exceptions. Maybe this is related. The problem
has to do with the JS method devmode uses to execute the JSNI code in the
browser. The stupid JS spec says if an object is null just do nothing, When
executing the JS for real this method isn't used and you get an error.
On Monday, July 16, 2012 8:47:29 PM UTC-4, Sean wrote:
>
> So I made a bone head mistake and had a null pointer error. essentially I
> had
>
> user = loadUser();
>
> if( user == null)
> {
> Make login screen
> }
> else{
> populate user
> }
>
> if(user.name == Sean)
> {
> do something
> }
>
> So obviously that nulls out if I'm not logged in. Here's the rub, it
> worked fine in development mode. It didn't toss an error or anything. When
> I deployed it, I was met with no errors, only a blank screen. However,
> Firefox worked fine. This took me HOURS to figure out.
>
> Any idea why it works in dev mode and FireFox? I wish it stopped working
> ASAP (like it should) so I know, Oh, that line I just put in made it stop
> working instead of it happening hours later when I'm deploying it.
>
>
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/2crD0bSMWkwJ.
To post to this group, send email to google-web-toolkit@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.
