On Fri, May 8, 2009 at 5:50 PM, ant elder <[email protected]> wrote: > On Fri, May 8, 2009 at 5:15 PM, Simon Laws <[email protected]> wrote: >> On Fri, May 8, 2009 at 5:07 PM, Simon Laws <[email protected]> wrote: >>> On Fri, May 8, 2009 at 5:00 PM, ant elder <[email protected]> wrote: >>>> On Fri, May 8, 2009 at 4:43 PM, Simon Laws <[email protected]> >>>> wrote: >>>>> On Fri, May 8, 2009 at 4:39 PM, Simon Laws <[email protected]> >>>>> wrote: >>>>>> On Fri, May 8, 2009 at 4:33 PM, ant elder <[email protected]> wrote: >>>>>>> On Fri, May 8, 2009 at 4:16 PM, Simon Laws <[email protected]> >>>>>>> wrote: >>>>>>>>> >>>>>>>>> Yes its the first of those. The sample/helloworld-bpel will show the >>>>>>>>> problem, if running in eclipse you need to build with mvn first so >>>>>>>>> that the Ode database gets unzipped into target\test-classes folder >>>>>>>>> and added to the classpath. >>>>>>>>> >>>>>>>>> ...ant >>>>>>>>> >>>>>>>> >>>>>>>> K, I don't even get that far. I get a NPE on the reference side >>>>>>>> running helloworl-bpel. Just updating again to make sure I've not >>>>>>>> missed anything. >>>>>>>> >>>>>>>> Simon >>>>>>>> >>>>>>> >>>>>>> Everything i have is checked in now so it should be working, what is >>>>>>> the NPE you get? >>>>>>> >>>>>>> ...ant >>>>>>> >>>>>> It did pick up a few things in the update so let me recompile and see >>>>>> if it goes away (fingers crossed). >>>>>> >>>>>> Simon >>>>>> >>>>> Right, got past one problem with an unneeded import but now have >>>>> problems with binding-rmi-runtime and node-laucher-equinox. Are you >>>>> getting a clean build? >>>>> >>>>> Simon >>>>> >>>> >>>> I've not done a full build since earlier, will do one now... >>>> >>>> ...ant >>>> >>> Right, I'm getting a bit further. After much messing about with >>> Eclipse I'm getting past the node-laucher-equinox problem at least. >>> Waiting for the rest of the build to complete. I seem to have all >>> kinds of problems when modules are moved around and I then try and to >>> so a maven build with Eclipse open. It's difficult to put my finger on >>> it but sorting the Eclipse build out means that mvn works properly? >>> >>> Simon >>> >> OK, things are looking better now. Basically a clean build. When I run >> samples/helloworld-bpel I still get the following. I'll run it up in >> the debugger. >> >> ------------------------------------------------------- >> T E S T S >> ------------------------------------------------------- >> Running helloworld.BPELHelloWorldTestCase >> 08-May-2009 17:13:07 org.apache.tuscany.sca.node.impl.NodeImpl <init> >> INFO: Creating node: default >> 08-May-2009 17:13:08 org.apache.tuscany.sca.node.impl.NodeImpl configureNode >> INFO: Loading contribution: >> file:/C:/simon/tuscany/java-trunk/sca/samples/hellow >> orld-bpel/target/classes/ >> 08-May-2009 17:13:08 org.apache.tuscany.sca.node.impl.NodeImpl start >> INFO: Starting node: default >> 08-May-2009 17:13:13 org.apache.tuscany.sca.node.impl.NodeImpl stop >> INFO: Stopping node: default >> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 5.813 sec >> <<< FA >> ILURE! >> testInvoke(helloworld.BPELHelloWorldTestCase) Time elapsed: 5.781 sec <<< >> ERRO >> R! >> java.lang.NullPointerException >> at >> org.apache.tuscany.sca.core.invocation.impl.JDKInvocationHandler.invo >> ke(JDKInvocationHandler.java:313) >> at >> org.apache.tuscany.sca.core.invocation.impl.JDKInvocationHandler.invo >> ke(JDKInvocationHandler.java:157) >> at $Proxy17.hello(Unknown Source) >> at >> helloworld.BPELHelloWorldTestCase.testInvoke(BPELHelloWorldTestCase.j >> ava:59) >> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >> at >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. >> java:39) >> at >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces >> sorImpl.java:25) >> at java.lang.reflect.Method.invoke(Method.java:597) >> at junit.framework.TestCase.runTest(TestCase.java:168) >> at junit.framework.TestCase.runBare(TestCase.java:134) >> at junit.framework.TestResult$1.protect(TestResult.java:110) >> at junit.framework.TestResult.runProtected(TestResult.java:128) >> at junit.framework.TestResult.run(TestResult.java:113) >> at junit.framework.TestCase.run(TestCase.java:124) >> at junit.framework.TestSuite.runTest(TestSuite.java:232) >> at junit.framework.TestSuite.run(TestSuite.java:227) >> > > I've a local patch to get passed this so need to remove that to > confirm but i think thats caused by this problem and if you set a > break point at getInterfaceContract or in the BPELInvoker you can see > this underlying problem that that NPE is hiding. > > ...ant >
Hi Ant Yep, I worked through to the actual problem. The underlying cause is that we haven't finished rolling out all of the Endpoint changes yet. I put a fix in to allow us to take a break before replacing all the existing EnpointReference structures with EndpointReference2 and Endpoint. Obviously my fix wasn't good enough. I'll take a look and see if I can fix the fix. Simon
