I'm getting an intermittent NPE in the binding-jsonp-runtime unit
test. Failed on full build worked on local build unfortunately
Tests run: 5, Failures: 0, Errors: 2, Skipped: 1, Time elapsed: 1.75
sec <<< FAILURE!
testReference(test.BindingTestCase) Time elapsed: 0.016 sec <<< ERROR!
java.l
On Fri, Sep 10, 2010 at 9:32 AM, Simon Laws wrote:
> I'm getting an intermittent NPE in the binding-jsonp-runtime unit
> test. Failed on full build worked on local build unfortunately
>
> Tests run: 5, Failures: 0, Errors: 2, Skipped: 1, Time elapsed: 1.75
> sec <<< FAILURE!
> testReference(te
>
> 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 delegat
On Fri, Sep 10, 2010 at 9:52 AM, Simon Laws 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
On Tue, Sep 14, 2010 at 3:41 PM, Simon Laws wrote:
> On Fri, Sep 10, 2010 at 9:52 AM, Simon Laws 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 he
On Tue, Sep 14, 2010 at 4:00 PM, ant elder wrote:
> On Tue, Sep 14, 2010 at 3:41 PM, Simon Laws wrote:
>> On Fri, Sep 10, 2010 at 9:52 AM, Simon Laws
>> wrote:
Yes i see the same for some days now. Its quite random, rerunning the
tests over and over with mvn or eclipse and someti
Another issue that's cropped up with this JSONP refactoring is that
the JSONP model now depends on the implementation class for the HTTP
model. This isn't reflected in the OSGi manisfests. For now I'll add
them in but it's not great to be exposing the impl classes of a
binding model as an SPI. JSON