Asankha C. Perera wrote:
Hi
I found the issue with our own code.. the public HttpService(final
HttpServerConnection conn) constructor of the HttpService class
available in alpha 2 is no longer available in alpha 3 (and later)..
without being deprecated :-( .. hence actually the Axis2 server throws
up a NoSuchMethodFound which leads the client to timeout.
asankha
Hi Asankha
I am sorry about inconveniences this has caused you
I submitted a patch intended to upgrade Axis2 to HttpCore 4.0 ALPHA-3
[1] the same very day HttpCore 4.0a3 was released. Unfortunately the
patch still has not been reviewed and checked in by the Axis folks.
We will start maintaining API compatibility between releases as of
BETA-1. At this point we still would like to have the liberty of
changing the public interfaces if new requirements are discovered or if
we see a better (cleaner) way to get the job done. Chances are good
ALPHA-4 will be the last alpha release of HttpCore. Actually I
personally think we can start thinking about the API freeze as soon as
we are reasonably sure HttpCore NIO API is sane.
Oleg
[1] http://issues.apache.org/jira/browse/AXIS2-1848
Asankha C. Perera wrote:
Hi Ortwin, all
I am having a dependency on the HttpClient as well for my project and
building the latest off the SVN for HttpCore (i.e.
4.0-alpha4-SNAPSHOT) causes a read timeout.. the version of
HttpClient being used is 3.0.1. Is there any known issues with this
version of the HttpClient and the latest HttpCore (i.e.
4.0-alpha4-SNAPSHOT)
Everything seems to work fine when HttpClient 3.0.1 is used with
HttpCore 4.0-alpha2 though.. so I am just wondering if this is a
known issue
thanks
asankha
---------------------------------------------------------------------
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]
