Another issue is the simple example, when copy groovy.xml to the
<SMX_HOME>/deploy, in the console we get the expected output
Starting JSR-223 groovy processor
org.apache.servicemix.jbi.runtime.impl.inonlyi...@13072d
Hello, I got an input message <?xml version="1.0" encoding="UTF-8"
standalone="no"?><timer><name>{http://servicemix.apache.org/examples/groovy}service:endpoint</name><group>DEFAULT</group><fullname>DEFAULT.{http://servicemix.apache.org/examples/groovy}service:endpoint</fullname><description/><fireTime>Mon
Mar 23 14:33:40 CST 2009</fireTime></timer>
But in the data/log/servicemix.log we also get exception like
14:11:10,683 | ERROR | ripting-thread-3 |
ScriptingEndpoint | emix.scripting.ScriptingEndpoint 309
| Error executing the script: null at line: -1 and column: -1
javax.script.ScriptException: Cannot invoke method get() on null object
at
com.google.code.scriptengines.groovy.GroovyScriptEngine.eval(GroovyScriptEngine.java:216)
at
com.google.code.scriptengines.groovy.GroovyCompiledScript.eval(GroovyCompiledScript.java:49)
at javax.script.CompiledScript.eval(CompiledScript.java:44)
at
org.apache.servicemix.scripting.ScriptingEndpoint.process(ScriptingEndpoint.java:300)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:627)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:581)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchangeInTx(AsyncBaseLifeCycle.java:478)
at
org.apache.servicemix.common.AsyncBaseLifeCycle$2.run(AsyncBaseLifeCycle.java:347)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException: Cannot invoke method get() on
null object
at
org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77)
at
org.codehaus.groovy.runtime.InvokerHelper.invokePogoMethod(InvokerHelper.java:784)
at
org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:758)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodN(ScriptBytecodeAdapter.java:170)
at Script1.run(Script1.groovy:13)
at
com.google.code.scriptengines.groovy.GroovyScriptEngine.eval(GroovyScriptEngine.java:213)
... 10 more
14:11:10,684 | ERROR | ripting-thread-3 |
ScriptingComponent | icemix.common.AsyncBaseLifeCycle 480
| Error processing exchange
org.apache.servicemix.jbi.runtime.impl.inonlyi...@818616
javax.script.ScriptException: Cannot invoke method get() on null object
at
com.google.code.scriptengines.groovy.GroovyScriptEngine.eval(GroovyScriptEngine.java:216)
at
com.google.code.scriptengines.groovy.GroovyCompiledScript.eval(GroovyCompiledScript.java:49)
at javax.script.CompiledScript.eval(CompiledScript.java:44)
at
org.apache.servicemix.scripting.ScriptingEndpoint.process(ScriptingEndpoint.java:300)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.doProcess(AsyncBaseLifeCycle.java:627)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchange(AsyncBaseLifeCycle.java:581)
at
org.apache.servicemix.common.AsyncBaseLifeCycle.processExchangeInTx(AsyncBaseLifeCycle.java:478)
at
org.apache.servicemix.common.AsyncBaseLifeCycle$2.run(AsyncBaseLifeCycle.java:347)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:595)
Caused by: java.lang.NullPointerException: Cannot invoke method get() on
null object
at
org.codehaus.groovy.runtime.NullObject.invokeMethod(NullObject.java:77)
at
org.codehaus.groovy.runtime.InvokerHelper.invokePogoMethod(InvokerHelper.java:784)
at
org.codehaus.groovy.runtime.InvokerHelper.invokeMethod(InvokerHelper.java:758)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodN(ScriptBytecodeAdapter.java:170)
at Script1.run(Script1.groovy:13)
at
com.google.code.scriptengines.groovy.GroovyScriptEngine.eval(GroovyScriptEngine.java:213)
... 10 more
Guillaume Nodet wrote:
I'd go for #2.
2009/3/22 Freeman Fang <[email protected]>:
Hi Guillaume,
SMXKNL-249 should fix it.
And as workaround in features, put wss4j bundle before cxf bundle also works.
Since currently if feature have inner feature dependency and bundles, it always
install the inner feature first, but wss4j bundle is in servciemix-cxf-bc
feature but not the cxf feature, so it means the workaound could be
1. we can't reuse cxf feature inside servicemix-cxf-bc feature, we need
explicitly include all bundles cxf feature have in servicemix-cxf-bc feature,
and ensure wss4j bundle before cxf bundle,
2 Or we need move wss4j bundle (and xmlsec bundle which is needed for wss4j)
from servicemix-cxf-bc feature to cxf feature before the cxf-bunlde.
Which way do you think is correct? I think put wss4j and xmlsec bundle to cxf
feature maybe better, even it's optional dependency, but not sure it will bring
any side-effect.
Thanks
Freeman
Guillaume Nodet wrote:
So that means that the WS security bundle is installed after cxf, it
should be installed before. SMX4KNL-249 would also sove the problem i
guess.
On Sun, Mar 22, 2009 at 01:29, Freeman Fang <[email protected]> wrote:
Hi Guillaume,
Yeah, after restarting servicemix, this example works again.
Freeman
Guillaume Nodet wrote:
Does it change anything if you restart servicemix (without deleting
the data folder) ?
This could indicate a wrong installation order of bundles with an
optional package not resolved.
On Sat, Mar 21, 2009 at 14:21, Freeman Fang <[email protected]>
wrote:
Hi Guillaume,
I can't believe you release so much things in one day! :-)
Just found cxf-wsdl-first example doesn't work in 4.0 kit.
The error is like
<component-name>servicemix-cxf-bc</component-name>
<component-task-result-details>
<task-result-details>
<task-id>deploy</task-id>
<task-result>FAILED</task-result>
<message-type>ERROR</message-type>
<task-status-msg><msg-loc-info><loc-token/><loc-message>Could not deploy
xbean service unit</loc-message></msg-loc-info></task-status-msg>
<exception-info>
<nesting-level>1</nesting-level>
<msg-loc-info>
<loc-token />
<loc-message>org/apache/ws/security/handler/WSHandler</loc-message>
<stack-trace><