On Fri, Sep 10, 2010 at 9:52 AM, Simon Laws <[email protected]> wrote:
>>
>> Yes i see the same for some days now. Its quite random, rerunning the
>> tests over and over with mvn or eclipse and sometimes it works fine
>> other times it gets the NPE with the head invoker null.
>>
>> Not certain but i think it started happening after the jsonp binding
>> was changed to delegate to the http binding runtime.
>>
>> ...ant
>>
>
> Interesting. No idea if this has any relevance but when that did
> happen I did get this strange dependency error relating to
> jsonp-runtime depending on something like host-http (looking back
> through mails now). Which I couldn't satisfactorily explain. I think
> you fixed it by adding the dependency but it did look a bit odd at the
> time.
>
> Simon
>
> --
> Apache Tuscany committer: tuscany.apache.org
> Co-author of a book about Tuscany and SCA: tuscanyinaction.com
>
I'm making some progress on this. The NPE is actually caused by this
line in the HTTPBindingProviderFactory...
public ReferenceBindingProvider
createReferenceBindingProvider(RuntimeEndpointReference
endpointReference) {
// Binding HTTP is currently NOT supporting References
return null;
}
The reason the problem is random is that the JSONP model sometimes
picks up the HTPPBindingProviderFactory and sometimes picks up the
JSONPBindingProviderFactory.
What was the actual intention re. the aggregation of JSONP and HTTP bindings?
Simon
--
Apache Tuscany committer: tuscany.apache.org
Co-author of a book about Tuscany and SCA: tuscanyinaction.com
