On Fri, May 8, 2009 at 3:20 PM, ant elder <[email protected]> wrote: > I'm trying to get implementation.bpel working in 2.x where its failing > as the Operation given to the BPELInvoker is a JavaOperation not a > WSDLOperation as expected. > > This is coming from the target operation from > RuntimeWireImpl2.initInvocationChains which is getting it from the > InterfaceContract determined by > CompositeActivatorImpl2.addReferenceWire from the getInterfaceContract > method. I'm not sure i understand what the getInterfaceContract method > is trying to do? The ComponentReference its given has a target service > with the correct WSDLInterfaceContract so shouldn't > getInterfaceContract be taking that into account? > > ...ant >
There's something I can't quite grasp here. Is your scenario something like... Java component -> Reference -> binding.sca -> binding.sca -> Service -> BPEL component or is it... Java component -> Reference -> binding.ws -> binding.ws -> Service -> BPEL component You have a problem in the BPELInvoker but you tracked the source of the offending operation to the reference wire. Sounds odd. I'm guessing something has got messed up in the binding.sca optimization (assuming you have the first scenario). Can you point me at the test that fails? Simon
