The problem still persists when I shut off JS/CSS compression, also,
there are no different JARs as I had thought (our build.xml slightly
renames a couple of them from the Maven JAR names, I fixed that in my
last commit today.) Running the Eclipse debugger was inconclusive (some
strange messages during code tracing, for example that it couldn't find
the unneeded-in-production Selenium source code). I'm guessing there's
a corruption in my local Maven repository, that has happened a few times
on other apps I've worked with. I'll clear it out and try again.
Glen
On 04/29/2013 11:52 AM, Dirk Frederickx wrote:
Glen,
"2) The compressed JS and CSS ..."
I would not expect a java exception on a compressed js/css file , and
certainly not related to the rendering of the JSP.
Try turning off the compression to see if the error persists.
dirk
On Mon, Apr 29, 2013 at 4:27 PM, Glen Mazza <glen.ma...@gmail.com> wrote:
Hi Team, I'll look more into it (hopefully someone else might quickly see
the error though), but the User Preferences page ("My Prefs" in upper-right
corner) works with the Ant WAR but not the Maven WAR. The app returns this
error with the latter:
"JSPWiki has detected an error
Error Message
in is null
Exception
java.lang.NullPointerException
Place where detected
java.util.zip.ZipInputStream.(**), line 100 "
I'm not getting any additional logging messages from either the JSPWiki
log or the Tomcat catalina.out log file. I don't think this page ever
worked with the Mavenized version, this was just the first time I noticed
it. I've done a "diff -r" on the expanded Ant and Maven JSPWiki WARs (as
well as the underlying JSPWiki JAR), there are very few differences
reported:
1.) Some minor naming differences with very few of the JARs -- Maven has a
few more JARs than the Ant version, and the same JAR can have a different
names in some cases between the two WARs, I'll standardize more where I can
on the JARs next.
2.) The compressed JavaScript and CSS files are different (hard to say how
much) -- the YUICompressor tool version we're using for that is newer in
Maven and maybe the new compression is causing problems with the JSP
rendering.
Another possible issue is that I'm missing some security or user-specific
configuration in the Maven WAR (which could be why the other pages are
rendering but not this user-specific one.)
Regards,
Glen
