No worries. I agree with you that connection.getProtocol().getScheme() is where the NPE is occuring. This means that either the connection or the protocol are null. From looking through the code and running various tests I am unsure of how this could happen. My guess is that the cause is how VFS is configuring/using HttpClient. If you could help to shed some light on what VFS is attempting I'm sure we will be able to find a solution.
Thanks,
Mike
Adam R. B. Jack wrote:
Mike wrote:
I must disagree with you here. I responded to your bug report about 5 hours after you posted it. I was unable to reproduce this problem given the details you have provided. If you have some more detail about how to reproduce this problem, or perhaps a wire log, I would be happy to continue helping.
<http://issues.apache.org/bugzilla/show_bug.cgi?id=22800>
Hmm, sorry Mike, I don't beleive I received notification of that. I certainly wasn't aware of the response. Sorry I didn't go look.
The crash that I get (still w/ latest CVS HEAD) is that in HttpMethodDirector.procesRedirectResponse the connection returns null fir pretty much everything, including Protocol. As such it crashes in: connection.getProtocol().getScheme() on line 460.
I will take your sample and attempt to reproduce it here. Unfortunately (for debugging this) I am using Commons VFS, which in turn uses HttpClient, so maybe it is some usage/re-usage/configuration sequence that causes this. I will see what I can do to reproduce.
regards,
Adam
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
