[
https://issues.apache.org/jira/browse/AXIS2-6051?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860030#comment-17860030
]
Michael Suhr commented on AXIS2-6051:
-------------------------------------
{code:java}
> [ntcore.common.session.impl.WebExceptionHandlerBean.internalResolveException
> ](tionHandlerBean.java: 360) Error:'void
> org.apache.hc.core5.http.impl.io.DefaultHttpResponseParserFactory.<init>(org.apache.hc.core5.http.config.Http1Config)'
> java.lang.NoSuchMethodError: 'void
> org.apache.hc.core5.http.impl.io.DefaultHttpResponseParserFactory.<init>(org.apache.hc.core5.http.config.Http1Config)'
> at
> org.apache.axis2.transport.http.impl.httpclient5.HTTPSenderImpl.getHttpClient(HTTPSenderImpl.java:170)
> at
> org.apache.axis2.transport.http.impl.httpclient5.HTTPSenderImpl.createRequest(HTTPSenderImpl.java:67)
> at
> org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:155)
> at
> org.apache.axis2.transport.http.AbstractHTTPTransportSender.writeMessageWithCommons(AbstractHTTPTransportSender.java:390)
> at
> org.apache.axis2.transport.http.AbstractHTTPTransportSender.invoke(AbstractHTTPTransportSender.java:214)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:431)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:399)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:225)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:150)
{code}
Hi, it's the constructor
`org.apache.hc.core5.http.impl.io.DefaultHttpResponseParserFactory.<init>(org.apache.hc.core5.http.config.Http1Config)`
It was introduced with 5.3 which beta currently. But usage of older 5.x will
fail.
> Axis2 Future Roadmap in keeping up with new Java Versions
> ---------------------------------------------------------
>
> Key: AXIS2-6051
> URL: https://issues.apache.org/jira/browse/AXIS2-6051
> Project: Axis2
> Issue Type: Wish
> Affects Versions: 1.8.0
> Reporter: Jeff Thomas
> Assignee: Robert Lazarski
> Priority: Major
> Fix For: 1.8.3
>
>
> Related to AXIS2-6035.
> Hi Robert/Andreas/Axis2 Support,
> just a general question about the realistic future of Axis2 (and by extension
> Axiom/Rampart) in keeping up with the quickly changing Java releases.
> We are getting a lot of push from our customers (and our own internal wish to
> use modern java features) to move to java 17+ ... we are hitting more and
> more walls with things like:
> * java modules
> * javax -> jakarta migration // this is a big one!
> ** jakarta.activation
> ** jakarta.validation
> ** jakarta.jms
> ** jakarta.mail
> ** jakarta.jws
> ** jakarta.jaxb
> ** ...
> * Tomcat 10 +
> * and related stuff like
> ** ActiveMQ Artemis (jakarta.jms)
> ** removal of SecurityManager in JDK 19+
> ** etc.
> The sort of general feeling is that unfortunately we are getting pulled
> towards a state of complete incompatibility between Axis2 and current
> supported JVMs / other Frameworks.
> Maybe you can give a bit of feedback about the roadmap for Axis2 and
> addressing the growing gap in dependencies? (and would welcome any info
> about Axiom/Rampart along the same lines). Good or bad news doesn't
> matter...would appreciate having some concrete statement to address our own
> internal planning about the way forward. :)
> Appreciate any info you can provide.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
