[news.eclipse.technology.ohf] Re: Query Document Failure using the OHF

[Matthew Davis <mattadav@xxxxxxxxxx>]

Jason,

Must've been an older version of the source code.  Indeed I was wanting 
you to comment out the section dealing with the HTTP protocol.  Or, more 
specifically, the lines:

//sProtocol = new Protocol("http", (new 
//OHFSocketFactoryWrapper(agent.getSocket(mEndpoint,false))),80);
//Protocol.registerProtocol("http", sProtocol);

The HTTP Client should then revert to creating its own socket for the 
HTTP request and obey proxy settings.

-Matt




Jason wrote:
> Hi Matt
>
> Line 194-196 in the AbstractOHFSOAPSender is actually the TLS part which 
> currently never gets reached because of the Non-TLS tests. So, after
> debuging only the code in the else part is reached.
> if (isDoingTLS()) {
> 194-196: sProtocol = new Protocol("https", (new 
> OHFSocketFactoryWrapper(agent.getSocket(mEndpoint, true))), 443);
> Protocol.registerProtocol("https", sProtocol);
> } else {
> ... here we go:
>
> Problem Section: Socket s1 = agent.getSocket(mEndpoint, false);
> OHFSocketFactoryWrapper ofw =  new OHFSocketFactoryWrapper(s1);
> sProtocol = new Protocol("http", ofw, 80);
> Protocol.registerProtocol("http", sProtocol);
> }
>
> Consequently i did also another tests on it.
>
> 1) My first thought was, that the proxy is is no capable of the current 
> http chunked setting. So i tried both .. disabled and enabled.
> 2) Reading the proxy access and error protocol after sending the 
> message. Well, it seems that the proxy never gets reached using the 
> original sourcecode. The funny thing is that the proxy settings are 
> correct set because they also in use for the ITI-14(own) and ITI-15 
> transaction. I have also debuged the proxy settings at the line 194 and 
> seems to be ok.
>
> Actually i have already found a workaround which seems to work by just 
> replacing the sending part of the B_Consumer Class with my own sending 
> class. With this solution everything seems to work properly with the 
> original NIST registry.
> My own sender class now uses the sendReceive method of the 
> org.apache.axis2.client.ServiceClient package with the settings 
> options.setProperty(AddressingConstants.DISABLE_ADDRESSING_FOR_OUT_MESSAGES, 
> true); and
> options.setProperty(HTTPConstants.CHUNKED, false);
>
> All tests are done as non-TLS
>
> Thanks for helping
> Jason