Re: [pebble-user] NPEs when loading css/js

[Brendan M. <pe...@bd...>]

> > I don't know how much servlets/JSP experience you have, but basically,
> > the "filters" defined in the /WEB-INF/web.xml file (e.g.
> > TransformingFilter, DispatchingFilter, GZIPFilter) are executed upon
> > every request. 

> > There shouldn't be much happening for the CSS and JS
> > files though because they are publicly accessible from the web
> > application (i.e. they are served up directly).

I looked at web.xml again.  GZIPFilter is set to apply on REQUESTs
for *.html, *.js, and *.css from the looks of it.  So does that mean
GZIPFilter is "invoked" every time one of those files is requested by
the browser?

It seems this is the case.  I hit

http://pebbletest.com:8080/pebble.css

in my browser.  The first time I got the css file displayed (as text).
I hit Ctrl-R to reload in my browser (Firefox2).  Then I got a page that
displayed 

       My blog
Error | Sorry , there has been a problem with your request.

And NPEs galore in the stderr/stdout log.

If I continue to hit Ctrl-R (or click the browser reload button), I
alternate between a styled version of the text above (with "My blog" in
a 40px or so font) and an unstyled version (with "My blog" completely
unstyled).  View Source shows, indeed, the contents of pebble.css.

If I put the cursor in the address bar (behind pebble.css) and hit
"enter", then the contents of pebble.css are once again display
correctly.

At this point, I don't know if it's Jetty or Firefox.  But I really
don't want to use Tomcat (as I have run Tomcat for years and would like
some experience with something else), and most of my expected traffic is
going to come from firefox (maybe, who knows--the site isn't live yet).

Thinking it was Firefox, I tried Safari.  No problem.  Was able to
reload /pebble.css all night long with no trouble or GZIPResponseWrapper
NPE.

There's a lightweight (to the point of being ridiculously feature-free
an kind of ugly) browser called dillo.  Loaded /pebble.css with dillo
over and over--no problem.

Another browser, galeon, however, produced the same 

Nested in javax.servlet.ServletException: java.lang.NullPointerException:
java.lang.NullPointerException
	at net.sourceforge.pebble.web.filter.GZIPResponseWrapper.flushBuffer(GZIPResponseWrapper.java:70)
 
and behaves exactly like firefox.  It is interesting to note that galeon 
is also gecko-based, using the same rendering and networking engines.  
Is there something to this?  

I suppose all you Tomcat-abiding users have no problems from
Firefox/Gecko....

Any light to be shed would be appreciated.

Brendan