[jira] [Updated] (CXF-8549) Get rid of EasyMock
[ https://issues.apache.org/jira/browse/CXF-8549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8549: -- Fix Version/s: 4.0.2 > Get rid of EasyMock > > > Key: CXF-8549 > URL: https://issues.apache.org/jira/browse/CXF-8549 > Project: CXF > Issue Type: Sub-task >Affects Versions: 3.4.4, 3.3.11 >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 4.0.2 > > > Get rid of EasyMock in favor of Mockito since it does require additional > access to sealed JDK internals for JDK-16 and above. > > [ ] ./core/pom.xml > [ ] ./integration/jca/pom.xml > [ ] ./rt/bindings/coloc/pom.xml > [ ] ./rt/bindings/corba/pom.xml > [ ] ./rt/bindings/soap/pom.xml > [ ] ./rt/databinding/aegis/pom.xml > [ ] ./rt/databinding/jaxb/pom.xml > [ ] ./rt/features/clustering/pom.xml > [ ] ./rt/features/logging/pom.xml > [ ] ./rt/features/throttling/pom.xml > [ ] ./rt/frontend/jaxrs/pom.xml > [ ] ./rt/frontend/jaxws/pom.xml > [ ] ./rt/frontend/js/pom.xml > [ ] ./rt/management/pom.xml > [ ] ./rt/rs/client/pom.xml > [ ] ./rt/rs/description/pom.xml > [ ] ./rt/rs/extensions/providers/pom.xml > [ ] ./rt/rs/extensions/search/pom.xml > [ ] ./rt/rs/microprofile-client/pom.xml > [ ] ./rt/rs/security/oauth-parent/oauth2/pom.xml > [ ] ./rt/rs/security/oauth-parent/oauth2-saml/pom.xml > [ ] ./rt/rs/security/sso/oidc/pom.xml > [ ] ./rt/transports/http/pom.xml > [ ] ./rt/transports/http-jetty/pom.xml > [ ] ./rt/transports/http-netty/netty-client/pom.xml > [ ] ./rt/transports/http-netty/netty-server/pom.xml > [ ] ./rt/transports/http-undertow/pom.xml > [ ] ./rt/transports/jms/pom.xml > [ ] ./rt/transports/websocket/pom.xml > [ ] ./rt/ws/addr/pom.xml > [ ] ./rt/ws/policy/pom.xml > [ ] ./rt/ws/rm/pom.xml > [ ] ./rt/ws/security/pom.xml > [ ] ./rt/ws/transfer/pom.xml > [ ] ./rt/wsdl/pom.xml > [ ] ./services/xkms/xkms-x509-handlers/pom.xml > [ ] ./services/xkms/xkms-x509-repo-ldap/pom.xml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8549) Get rid of EasyMock
[ https://issues.apache.org/jira/browse/CXF-8549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8549: -- Fix Version/s: 3.6.1 > Get rid of EasyMock > > > Key: CXF-8549 > URL: https://issues.apache.org/jira/browse/CXF-8549 > Project: CXF > Issue Type: Sub-task >Affects Versions: 3.4.4, 3.3.11 >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 4.0.2, 3.6.1 > > > Get rid of EasyMock in favor of Mockito since it does require additional > access to sealed JDK internals for JDK-16 and above. > > [ ] ./core/pom.xml > [ ] ./integration/jca/pom.xml > [ ] ./rt/bindings/coloc/pom.xml > [ ] ./rt/bindings/corba/pom.xml > [ ] ./rt/bindings/soap/pom.xml > [ ] ./rt/databinding/aegis/pom.xml > [ ] ./rt/databinding/jaxb/pom.xml > [ ] ./rt/features/clustering/pom.xml > [ ] ./rt/features/logging/pom.xml > [ ] ./rt/features/throttling/pom.xml > [ ] ./rt/frontend/jaxrs/pom.xml > [ ] ./rt/frontend/jaxws/pom.xml > [ ] ./rt/frontend/js/pom.xml > [ ] ./rt/management/pom.xml > [ ] ./rt/rs/client/pom.xml > [ ] ./rt/rs/description/pom.xml > [ ] ./rt/rs/extensions/providers/pom.xml > [ ] ./rt/rs/extensions/search/pom.xml > [ ] ./rt/rs/microprofile-client/pom.xml > [ ] ./rt/rs/security/oauth-parent/oauth2/pom.xml > [ ] ./rt/rs/security/oauth-parent/oauth2-saml/pom.xml > [ ] ./rt/rs/security/sso/oidc/pom.xml > [ ] ./rt/transports/http/pom.xml > [ ] ./rt/transports/http-jetty/pom.xml > [ ] ./rt/transports/http-netty/netty-client/pom.xml > [ ] ./rt/transports/http-netty/netty-server/pom.xml > [ ] ./rt/transports/http-undertow/pom.xml > [ ] ./rt/transports/jms/pom.xml > [ ] ./rt/transports/websocket/pom.xml > [ ] ./rt/ws/addr/pom.xml > [ ] ./rt/ws/policy/pom.xml > [ ] ./rt/ws/rm/pom.xml > [ ] ./rt/ws/security/pom.xml > [ ] ./rt/ws/transfer/pom.xml > [ ] ./rt/wsdl/pom.xml > [ ] ./services/xkms/xkms-x509-handlers/pom.xml > [ ] ./services/xkms/xkms-x509-repo-ldap/pom.xml -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CXF-6349) Introduce HTTP/2 Transport
[
https://issues.apache.org/jira/browse/CXF-6349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko resolved CXF-6349.
---
Resolution: Fixed
> Introduce HTTP/2 Transport
> ---
>
> Key: CXF-6349
> URL: https://issues.apache.org/jira/browse/CXF-6349
> Project: CXF
> Issue Type: New Feature
> Components: Transports
>Affects Versions: 3.4.5
>Reporter: Sergey Beryozkin
>Assignee: Andriy Redko
>Priority: Major
>
> [https://http2.github.io/]
> Can be complementary to what Aki has done with WebSockets.
> h2. Proposal
> All four web containers (Jetty / Tomcat / Undertow / Netty), which CXF
> integrates with, support HTTP/2 over TCP (h2c) and HTTP/2 over TLS (h2).
> Technically it is possible to only support HTTP/2 protocol [1], but
> practically both HTTP/1.1 and HTTP/2 always come together. As such, the it
> would make sense to enhance current CXF's `ServerEngine`s implementations to
> turn H2 (or H2C if TLS/SSL is not configured) on, in addition to HTTP/1.1,
> controllable by property:
> {noformat}
> org.apache.cxf.transports.http2.enabled = true | false{noformat}
> At the moment, only CXF's Undertow transport
> (`cxf-rt-transports-http-undertow`) allows to configure HTTP/2 support using
> `Bus` property `org.apache.cxf.transports.http_undertow.EnableHttp2`. The
> proposal is to deprecate this property for removal in favor of
> `org.apache.cxf.transports.http2.enabled` (semantic of this property would be
> kept the same). Meantime, both properties will be supported, see please
> official documentation updates [2].
> Since CXF also provides clients, it is expected to have H2 and H2C support
> for clients as well.
> [1]
> [https://http2.github.io/faq/#can-i-implement-http2-without-implementing-http11]
> [2] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191336305
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-8841) Enable HTTP/2 Transport by default: client-side support (Netty & HttpClient 5)
[ https://issues.apache.org/jira/browse/CXF-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8841: -- Issue Type: Improvement (was: Bug) > Enable HTTP/2 Transport by default: client-side support (Netty & HttpClient 5) > -- > > Key: CXF-8841 > URL: https://issues.apache.org/jira/browse/CXF-8841 > Project: CXF > Issue Type: Improvement >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.7.0 > > > The HTTP/2 is opt-in right now for Netty & HttpClient 5 async clients > (managed by *org.apache.cxf.transports.http2.enabled* property), it should be > allowed by default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8606) Introduce HTTP/2 Transport: client-side support (Netty & HttpClient 5)
[
https://issues.apache.org/jira/browse/CXF-8606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko updated CXF-8606:
--
Description:
[https://cwiki.apache.org/confluence/display/CXF20DOC/Asynchronous+Client+HTTP+Transport,
|https://cwiki.apache.org/confluence/display/CXF20DOC/Asynchronous+Client+HTTP+Transport]enabled
once org.apache.cxf.transports.http2.enabled bus/contextual property is set to
*true* (default is {*}false{*}). (was:
https://cwiki.apache.org/confluence/display/CXF20DOC/Asynchronous+Client+HTTP+Transport)
> Introduce HTTP/2 Transport: client-side support (Netty & HttpClient 5)
> --
>
> Key: CXF-8606
> URL: https://issues.apache.org/jira/browse/CXF-8606
> Project: CXF
> Issue Type: Sub-task
>Affects Versions: 3.4.5
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.11, 4.0.2, 3.5.7, 3.6.1
>
>
> [https://cwiki.apache.org/confluence/display/CXF20DOC/Asynchronous+Client+HTTP+Transport,
>
> |https://cwiki.apache.org/confluence/display/CXF20DOC/Asynchronous+Client+HTTP+Transport]enabled
> once org.apache.cxf.transports.http2.enabled bus/contextual property is set
> to *true* (default is {*}false{*}).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-8841) Enable HTTP/2 Transport by default: client-side support (Netty & HttpClient 5)
[ https://issues.apache.org/jira/browse/CXF-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8841: -- Description: The HTTP/2 is opt-in right now for Netty & HttpClient 5 async clients (managed by *org.apache.cxf.transports.http2.enabled* property), it should be allowed by default. (was: The HTTP/2 is opt-in right now for) > Enable HTTP/2 Transport by default: client-side support (Netty & HttpClient 5) > -- > > Key: CXF-8841 > URL: https://issues.apache.org/jira/browse/CXF-8841 > Project: CXF > Issue Type: Bug >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.7.0 > > > The HTTP/2 is opt-in right now for Netty & HttpClient 5 async clients > (managed by *org.apache.cxf.transports.http2.enabled* property), it should be > allowed by default. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CXF-8841) Enable HTTP/2 Transport by default: client-side support (Netty & HttpClient 5)
Andriy Redko created CXF-8841: - Summary: Enable HTTP/2 Transport by default: client-side support (Netty & HttpClient 5) Key: CXF-8841 URL: https://issues.apache.org/jira/browse/CXF-8841 Project: CXF Issue Type: Bug Reporter: Andriy Redko Assignee: Andriy Redko -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8841) Enable HTTP/2 Transport by default: client-side support (Netty & HttpClient 5)
[ https://issues.apache.org/jira/browse/CXF-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8841: -- Description: The HTTP/2 is opt-in right now for > Enable HTTP/2 Transport by default: client-side support (Netty & HttpClient 5) > -- > > Key: CXF-8841 > URL: https://issues.apache.org/jira/browse/CXF-8841 > Project: CXF > Issue Type: Bug >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.7.0 > > > The HTTP/2 is opt-in right now for -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8841) Enable HTTP/2 Transport by default: client-side support (Netty & HttpClient 5)
[ https://issues.apache.org/jira/browse/CXF-8841?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8841: -- Fix Version/s: 4.1.0 3.7.0 > Enable HTTP/2 Transport by default: client-side support (Netty & HttpClient 5) > -- > > Key: CXF-8841 > URL: https://issues.apache.org/jira/browse/CXF-8841 > Project: CXF > Issue Type: Bug >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0, 3.7.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8669) Multipart annotation not working 3.4.6 onwards.
[
https://issues.apache.org/jira/browse/CXF-8669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721573#comment-17721573
]
Andriy Redko commented on CXF-8669:
---
Documentation update:
https://cwiki.apache.org/confluence/display/CXF20DOC/JAX-RS+Multiparts
> Multipart annotation not working 3.4.6 onwards.
> ---
>
> Key: CXF-8669
> URL: https://issues.apache.org/jira/browse/CXF-8669
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.4.6, 3.5.5
>Reporter: Abhishek Rana
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.6.0, 4.0.1, 3.5.6, 3.4.11
>
>
> Hello Team,
> I have following API declaration
> {code:java}
> @POST
> @Path("/{configurationName}.diff")
> @Consumes(MediaType.MULTIPART_FORM_DATA)
> @Produces({MediaType.APPLICATION_JSON})
> ConfigurationDiffDTO diff(@PathParam("configurationName") String
> configurationName,
> @Multipart(value = "fromRev", required = false) Long fromRev,
> @Multipart(value = "toRev", required = false) Long toRev, @Multipart(value =
> "file", required = false) Attachment file);
> {code}
> Above declaration works fine till 3.4.5 , after I upgraded to 3.5.0 (even
> 3.4.6) , multipart form values (fromRev and toRev) they are coming as null.
> Is it a regression?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CXF-8669) Multipart annotation not working 3.4.6 onwards.
[
https://issues.apache.org/jira/browse/CXF-8669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721323#comment-17721323
]
Andriy Redko commented on CXF-8669:
---
Hi [~echatellier] ,
There is a way now to change the content type using
`org.apache.cxf.attachment.content-type` contextual / bus property
(https://cxf.apache.org/docs/bus-configuration.html), that you could set to
"text/plain" to preserve the older behavior. Thank you.
> Multipart annotation not working 3.4.6 onwards.
> ---
>
> Key: CXF-8669
> URL: https://issues.apache.org/jira/browse/CXF-8669
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.4.6, 3.5.5
>Reporter: Abhishek Rana
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.6.0, 4.0.1, 3.5.6, 3.4.11
>
>
> Hello Team,
> I have following API declaration
> {code:java}
> @POST
> @Path("/{configurationName}.diff")
> @Consumes(MediaType.MULTIPART_FORM_DATA)
> @Produces({MediaType.APPLICATION_JSON})
> ConfigurationDiffDTO diff(@PathParam("configurationName") String
> configurationName,
> @Multipart(value = "fromRev", required = false) Long fromRev,
> @Multipart(value = "toRev", required = false) Long toRev, @Multipart(value =
> "file", required = false) Attachment file);
> {code}
> Above declaration works fine till 3.4.5 , after I upgraded to 3.5.0 (even
> 3.4.6) , multipart form values (fromRev and toRev) they are coming as null.
> Is it a regression?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CXF-8669) Multipart annotation not working 3.4.6 onwards.
[
https://issues.apache.org/jira/browse/CXF-8669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17721249#comment-17721249
]
Eric Chatellier commented on CXF-8669:
--
Hi, I just tested the released 3.6.0 version, and this is still not working :(
I will try to debug it again...
> Multipart annotation not working 3.4.6 onwards.
> ---
>
> Key: CXF-8669
> URL: https://issues.apache.org/jira/browse/CXF-8669
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.4.6, 3.5.5
>Reporter: Abhishek Rana
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.6.0, 4.0.1, 3.5.6, 3.4.11
>
>
> Hello Team,
> I have following API declaration
> {code:java}
> @POST
> @Path("/{configurationName}.diff")
> @Consumes(MediaType.MULTIPART_FORM_DATA)
> @Produces({MediaType.APPLICATION_JSON})
> ConfigurationDiffDTO diff(@PathParam("configurationName") String
> configurationName,
> @Multipart(value = "fromRev", required = false) Long fromRev,
> @Multipart(value = "toRev", required = false) Long toRev, @Multipart(value =
> "file", required = false) Attachment file);
> {code}
> Above declaration works fine till 3.4.5 , after I upgraded to 3.5.0 (even
> 3.4.6) , multipart form values (fromRev and toRev) they are coming as null.
> Is it a regression?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
