[
https://issues.apache.org/jira/browse/EXTSCRIPT-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849714#action_12849714
]
Werner Punz commented on EXTSCRIPT-100:
---------------------------------------
Ok the NPE was caused by a starting jetty via run instead of run-exploded and
then not having alternative pickup paths set, I fixed the npe issue first by
replacing it with a warning, along the lines another bug was in the variable
resolver, a missing null check which nped orchestra in that area, fixed as
well, the demo project bruno is working on, now is running perfectly with
ext-scripting, full success.
> ExtSCRIPT + Jetty 7 NPEs at startup (jetty 6 works)
> ---------------------------------------------------
>
> Key: EXTSCRIPT-100
> URL: https://issues.apache.org/jira/browse/EXTSCRIPT-100
> Project: MyFaces Extensions Scripting
> Issue Type: Bug
> Affects Versions: Beta-1
> Reporter: Werner Punz
> Assignee: Werner Punz
> Fix For: 1.0-Beta-2
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
