Ok I fixed everything now in the trunk, the project now works with
Ext-Scripting.
There were several issues
a) A configuration issue, the filter was not set, this was an error on
my part in the docs, they will be updated as soon as the peoples server
is up again.
b) The project was started non expanded and alternative pickup paths
were not set. The NPE in that area however was ugly, I replaced it with
a severe warning. You can use Ext-Scripting non expanded but then
WEB-INF/<scriptingdir> is not picked up, you have to add alternative
pickup paths then.
c) There was a bug in the VariableResolverProxy which was not present in
the EL-Resolver, somehow Orchestra must have triggered that one, I fixed
it in the trunk, since the VariableResolver is legacy I see that as a
mediocre issue, no showstopper to withhold the Beta-1
Nevertheless I fixed everything in the trunk now and Brunos project
seems to run fine.
Thanks for helping me to debug all this out, if someone also has
integration issues please post it, I am willing to help because I want
to nail the bugs down now that we are in beta more or less.
Werner
Am 24.03.10 17:25, schrieb Werner Punz:
Ok I did a quick check on my jetty6 testcase, by renaming WEB-INF/groovy
to WEB-INF/groovy2 and I could not reproduce the NPE
so it is definitely jetty7s fault here, nevertheless I will add
a bypass and a warning message to cover that NPE for the next beta.
(and will look for ways to pick the dirs up nevertheless)
Werner
Am 24.03.10 17:17, schrieb Werner Punz:
Hi Bruno I checked the offending NPEing line,
what happens in your case seems to be following
String contextRoot = servletContext.getRealPath(defaultScriptingRoot);
>>> contextRoot = contextRoot.trim();
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.
It is either that Jetty returns a null here if the directories do not
exist (which is a bug in my case but not a showstopper to hold the
voting for the beta1, I just will add a documentation for the users)
or it is a bug in jetty (which I have yet to investigate, try to run it
in jetty6 or tomcat 6 in that case, this worked for me)
Werner
Am 24.03.10 14:57, schrieb Bruno Aranda:
Hi,
I was going to try but I am hitting this exception:
INFO: MyFaces Plugins found
24-Mar-2010 13:53:57
org.apache.myfaces.webapp.StartupServletContextListener
dispatchInitializationEvent
INFO: Processing
plugin:org.apache.myfaces.scripting.servlet.StartupServletContextPluginChainLoader
24-Mar-2010 13:53:57
org.apache.myfaces.scripting.servlet.StartupServletContextPluginChainLoader
preInit
INFO: [EXT-SCRIPTING] Instantiating
StartupServletContextPluginChainLoader
2010-03-24 13:53:57.421:WARN::Failed startup of context
jettywebappcont...@17072b90@17072b90/editor,file:/scratch/projects/intact-current/service/editor/src/main/webapp/;jar:file:/homes/baranda/.m2/repository/org/apache/myfaces/core/myfaces-api/2.0.0-beta-3/myfaces-api-2.0.0-beta-3.jar!/META-INF/resources;jar:file:/homes/baranda/.m2/repository/org/primefaces/primefaces/2.0.0/primefaces-2.0.0.jar!/META-INF/resources;,file:/scratch/projects/intact-current/service/editor/src/main/webapp/
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)
at
org.apache.myfaces.scripting.servlet.StartupServletContextPluginChainLoader.preInit(StartupServletContextPluginChainLoader.java:61)
at
org.apache.myfaces.webapp.StartupServletContextListener.dispatchInitializationEvent(StartupServletContextListener.java:116)
at
org.apache.myfaces.webapp.StartupServletContextListener.contextInitialized(StartupServletContextListener.java:154)
at
org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:645)
at
org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:189)
at
org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:978)
at
org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:586)
at
org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:349)
at
org.mortbay.jetty.plugin.JettyWebAppContext.doStart(JettyWebAppContext.java:102)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
at
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:165)
at
org.eclipse.jetty.server.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:162)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
at
org.eclipse.jetty.server.handler.HandlerCollection.doStart(HandlerCollection.java:165)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
at
org.eclipse.jetty.server.handler.HandlerWrapper.doStart(HandlerWrapper.java:92)
at org.eclipse.jetty.server.Server.doStart(Server.java:228)
at org.mortbay.jetty.plugin.JettyServer.doStart(JettyServer.java:69)
at
org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:55)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:433)
at
org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:377)
at org.mortbay.jetty.plugin.JettyRunMojo.execute(JettyRunMojo.java:546)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:569)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
I am using JSF 2 in jetty 7 and have configured the web.xml
context-params...
Any ideas?
Bruno
On 24 March 2010 08:24, Werner Punz <[email protected]
<mailto:[email protected]>> wrote:
Hi,
Leonardo and I were running the needed tasks to get the 1.0-beta-1
release of Apache MyFaces Extension Scripting out.
The artifacts are deployed to Leonardos private Apache account ([1]
and [3] for binary and source packages).
Since the documentation is a work in progress (the download links to
the beta-1 will be added after the release in the trunk and hence
currently not directly connected to the release cycle), it is hosted
under
http://people.apache.org/~werpu/ext-script-site/
and not yet directly linked from our mainpage.
The release notes could be found at [4].
Please take a look at the "2.0-beta-1" artifacts and vote!
Please note: This vote is "majority approval" with a minimum of three
+1 votes (see [3]).
------------------------------------------------
[ ] +1 for community members who have reviewed the bits
[ ] +0
[ ] -1 for fatal flaws that should cause these bits not to be released,
and why..............
------------------------------------------------
Thanks,
Werner Punz
[1] http://people.apache.org/~lu4242/extscript10beta1/
[2] http://www.apache.org/foundation/voting.html#ReleaseVotes
[3] http://people.apache.org/~lu4242/extscript10beta1binsrc
[4]
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310964&styleName=Html&version=12314859
<https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310964&styleName=Html&version=12314859>
