Thanks Simon, So we already support the mirror image case today where we need a WSDL intf for the binding but have only a Java intf in the component; we generate a WSDL if necessary.
So for the wf.jmsObject plus impl.bpel case, I suppose we could just generate Java as well. So each binding requiring this could, in all cases, call a new SPI named something like getJavaInterfaceContractForBinding() which would first look at the app for a Java interface, and if one is not present, we could generate one from the WSDL interface we would presumably have. I purposely phrased that as "look at the app for a Java interface" because I think we'd need to think through the details of which to look at: component interface, componentType interface, or possibly both. Scott
