[EXTSCRIPT-100] ExtSCRIPT + Jetty 7 NPEs at startup (jetty 6 works)

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Beta-1
• Fix Version/s: 1.0-Final
• Assignee: Werner Punz
• Reporter: Werner Punz
• Created: 24/Mar/10 16:34
• Updated: 13/Apr/11 09:31
• Resolved: 25/Mar/10 14:49

Description

Bruno Aranda has reported following

java.lang.NullPointerException
at
org.apache.myfaces.scripting.servlet.CustomChainLoader.setupScriptingPaths(CustomChainLoader.java:76)

at
org.apache.myfaces.scripting.servlet.CustomChainLoader.<init>(CustomChainLoader.java:63)

at
org.apache.myfaces.scripting.servlet.StartupServletContextPluginChainLoader.initChainLoader(StartupServletContextPluginChainLoader.java:116)

A further investigation on the codebase revealed that following happens

aka in reality it does following
String contextRoot = servletContext.getRealPath("/WEB-INF/groovy");
>>> contextRoot = contextRoot.trim();

The problem is that the code did not expect a null since it checks for a
standard /WEB-INF/java and /WEB-INF/groovy.

Now, a quick test under jetty 6 reveals that this never nulls, even if the directories do not exist, jetty 7s behavior seems to be worse in this regard, although this is a bug on jettys side, a bypass and a warning is needed so that the NPE does not occur anymore even if the paths cannot be resolved.