[jira] [Created] (CXF-8906) Upgrade, HTTP2-Settings - Apache-CXF/3.6.1
Giacomo Carnevale created CXF-8906:
--
Summary: Upgrade, HTTP2-Settings - Apache-CXF/3.6.1
Key: CXF-8906
URL: https://issues.apache.org/jira/browse/CXF-8906
Project: CXF
Issue Type: Bug
Components: JAX-WS Runtime, Soap Binding, Transports
Affects Versions: 3.6.1
Environment: Apache CXF 3.6.1
Apache Camel 3.21.0
Java 11
Reporter: Giacomo Carnevale
Fix For: 3.5.6
Hi
I am using Apache Camel CXF component to integrate soap services.
Recently, I updated Apache Camel Version (3.20.x -> 3.21.0) and so is changed
Apache CXF version (3.5.6 -> 3.6.1).
*CXF 3.6.1*
When I invoke SOAP service, by tcpdump I can see that CXF sets http headers
'{*}Connection: Upgrade, HTTP2-Settings{*}', '{*}HTTP2-Settings:
AAEAAEIBAAMAAABkAAQBAAUAAEAA{*}' and '{*}Upgrade: h2c{*}' but the
connection is HTTP/1.1:
{code:java}
.o.91v..POST /my-soap-service HTTP/1.1
Connection: Upgrade, HTTP2-Settings
Host: myhost:8080
HTTP2-Settings: AAEAAEIBAAMAAABkAAQBAAUAAEAA
Transfer-encoding: chunked
Upgrade: h2c
Accept: */*
Authorization: Basic **
Content-Type: text/xml; charset=UTF-8
SOAPAction: ""
User-Agent: Apache-CXF/3.6.1{code}
The server responds with {*}HTTP/1.1 101 Switching Protocols{*}.
*CXF 3.5.6*
I excluded CXF dependencies from Apache Camel and I downgraded it to 3.5.6
version and there wasn't this problem
{code:java}
.\X
POST /my-soap-service HTTP/1.1
Content-Type: text/xml; charset=UTF-8
Accept: */*
Authorization: Basic **
SOAPAction: ""
User-Agent: Apache-CXF/3.5.6
Cache-Control: no-cache
Pragma: no-cache
Host: my-host:8080
Connection: keep-alive
Transfer-Encoding: chunked {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-8906) Upgrade, HTTP2-Settings - Apache-CXF/3.6.1
[
https://issues.apache.org/jira/browse/CXF-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Carnevale updated CXF-8906:
---
Description:
Hi
I am using Apache Camel CXF component to integrate soap services.
Recently, I updated Apache Camel Version (3.20.x -> 3.21.0) and so Apache CXF
version is changed (3.5.6 -> 3.6.1).
*CXF 3.6.1*
When I invoke SOAP service, by tcpdump I can see that CXF sets http headers
'{*}Connection: Upgrade, HTTP2-Settings{*}', '{*}HTTP2-Settings:
AAEAAEIBAAMAAABkAAQBAAUAAEAA{*}' and '{*}Upgrade: h2c{*}' but the
connection is {*}HTTP/1.1{*}:
{code:java}
.o.91v..POST /my-soap-service HTTP/1.1
Connection: Upgrade, HTTP2-Settings
Host: myhost:8080
HTTP2-Settings: AAEAAEIBAAMAAABkAAQBAAUAAEAA
Transfer-encoding: chunked
Upgrade: h2c
Accept: */*
Authorization: Basic **
Content-Type: text/xml; charset=UTF-8
SOAPAction: ""
User-Agent: Apache-CXF/3.6.1{code}
The server responds with {*}HTTP/1.1 101 Switching Protocols{*}.
*CXF 3.5.6*
I excluded CXF dependencies from Apache Camel and I downgraded it to 3.5.6
version and there wasn't this problem
{code:java}
.\X
POST /my-soap-service HTTP/1.1
Content-Type: text/xml; charset=UTF-8
Accept: */*
Authorization: Basic **
SOAPAction: ""
User-Agent: Apache-CXF/3.5.6
Cache-Control: no-cache
Pragma: no-cache
Host: my-host:8080
Connection: keep-alive
Transfer-Encoding: chunked {code}
was:
Hi
I am using Apache Camel CXF component to integrate soap services.
Recently, I updated Apache Camel Version (3.20.x -> 3.21.0) and so Apache CXF
version is changed (3.5.6 -> 3.6.1).
*CXF 3.6.1*
When I invoke SOAP service, by tcpdump I can see that CXF sets http headers
'{*}Connection: Upgrade, HTTP2-Settings{*}', '{*}HTTP2-Settings:
AAEAAEIBAAMAAABkAAQBAAUAAEAA{*}' and '{*}Upgrade: h2c{*}' but the
connection is HTTP/1.1:
{code:java}
.o.91v..POST /my-soap-service HTTP/1.1
Connection: Upgrade, HTTP2-Settings
Host: myhost:8080
HTTP2-Settings: AAEAAEIBAAMAAABkAAQBAAUAAEAA
Transfer-encoding: chunked
Upgrade: h2c
Accept: */*
Authorization: Basic **
Content-Type: text/xml; charset=UTF-8
SOAPAction: ""
User-Agent: Apache-CXF/3.6.1{code}
The server responds with {*}HTTP/1.1 101 Switching Protocols{*}.
*CXF 3.5.6*
I excluded CXF dependencies from Apache Camel and I downgraded it to 3.5.6
version and there wasn't this problem
{code:java}
.\X
POST /my-soap-service HTTP/1.1
Content-Type: text/xml; charset=UTF-8
Accept: */*
Authorization: Basic **
SOAPAction: ""
User-Agent: Apache-CXF/3.5.6
Cache-Control: no-cache
Pragma: no-cache
Host: my-host:8080
Connection: keep-alive
Transfer-Encoding: chunked {code}
> Upgrade, HTTP2-Settings - Apache-CXF/3.6.1
> --
>
> Key: CXF-8906
> URL: https://issues.apache.org/jira/browse/CXF-8906
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime, Soap Binding, Transports
>Affects Versions: 3.6.1
> Environment: Apache CXF 3.6.1
> Apache Camel 3.21.0
> Java 11
>Reporter: Giacomo Carnevale
>Priority: Major
> Fix For: 3.5.6
>
>
> Hi
> I am using Apache Camel CXF component to integrate soap services.
> Recently, I updated Apache Camel Version (3.20.x -> 3.21.0) and so Apache CXF
> version is changed (3.5.6 -> 3.6.1).
> *CXF 3.6.1*
> When I invoke SOAP service, by tcpdump I can see that CXF sets http headers
> '{*}Connection: Upgrade, HTTP2-Settings{*}', '{*}HTTP2-Settings:
> AAEAAEIBAAMAAABkAAQBAAUAAEAA{*}' and '{*}Upgrade: h2c{*}' but the
> connection is {*}HTTP/1.1{*}:
> {code:java}
> .o.91v..POST /my-soap-service HTTP/1.1
> Connection: Upgrade, HTTP2-Settings
> Host: myhost:8080
> HTTP2-Settings: AAEAAEIBAAMAAABkAAQBAAUAAEAA
> Transfer-encoding: chunked
> Upgrade: h2c
> Accept: */*
> Authorization: Basic **
> Content-Type: text/xml; charset=UTF-8
> SOAPAction: ""
> User-Agent: Apache-CXF/3.6.1{code}
>
>
> The server responds with {*}HTTP/1.1 101 Switching Protocols{*}.
> *CXF 3.5.6*
> I excluded CXF dependencies from Apache Camel and I downgraded it to 3.5.6
> version and there wasn't this problem
> {code:java}
> .\X
> POST /my-soap-service HTTP/1.1
> Content-Type: text/xml; charset=UTF-8
> Accept: */*
> Authorization: Basic **
> SOAPAction: ""
> User-Agent: Apache-CXF/3.5.6
> Cache-Control: no-cache
> Pragma: no-cache
> Host: my-host:8080
> Connection: keep-alive
> Transfer-Encoding: chunked {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-8906) Upgrade, HTTP2-Settings - Apache-CXF/3.6.1
[
https://issues.apache.org/jira/browse/CXF-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Carnevale updated CXF-8906:
---
Description:
Hi
I am using Apache Camel CXF component to integrate soap services.
Recently, I updated Apache Camel Version (3.20.x -> 3.21.0) and so Apache CXF
version is changed (3.5.6 -> 3.6.1).
*CXF 3.6.1*
When I invoke SOAP service, by tcpdump I can see that CXF sets http headers
'{*}Connection: Upgrade, HTTP2-Settings{*}', '{*}HTTP2-Settings:
AAEAAEIBAAMAAABkAAQBAAUAAEAA{*}' and '{*}Upgrade: h2c{*}' but the
connection is HTTP/1.1:
{code:java}
.o.91v..POST /my-soap-service HTTP/1.1
Connection: Upgrade, HTTP2-Settings
Host: myhost:8080
HTTP2-Settings: AAEAAEIBAAMAAABkAAQBAAUAAEAA
Transfer-encoding: chunked
Upgrade: h2c
Accept: */*
Authorization: Basic **
Content-Type: text/xml; charset=UTF-8
SOAPAction: ""
User-Agent: Apache-CXF/3.6.1{code}
The server responds with {*}HTTP/1.1 101 Switching Protocols{*}.
*CXF 3.5.6*
I excluded CXF dependencies from Apache Camel and I downgraded it to 3.5.6
version and there wasn't this problem
{code:java}
.\X
POST /my-soap-service HTTP/1.1
Content-Type: text/xml; charset=UTF-8
Accept: */*
Authorization: Basic **
SOAPAction: ""
User-Agent: Apache-CXF/3.5.6
Cache-Control: no-cache
Pragma: no-cache
Host: my-host:8080
Connection: keep-alive
Transfer-Encoding: chunked {code}
was:
Hi
I am using Apache Camel CXF component to integrate soap services.
Recently, I updated Apache Camel Version (3.20.x -> 3.21.0) and so is changed
Apache CXF version (3.5.6 -> 3.6.1).
*CXF 3.6.1*
When I invoke SOAP service, by tcpdump I can see that CXF sets http headers
'{*}Connection: Upgrade, HTTP2-Settings{*}', '{*}HTTP2-Settings:
AAEAAEIBAAMAAABkAAQBAAUAAEAA{*}' and '{*}Upgrade: h2c{*}' but the
connection is HTTP/1.1:
{code:java}
.o.91v..POST /my-soap-service HTTP/1.1
Connection: Upgrade, HTTP2-Settings
Host: myhost:8080
HTTP2-Settings: AAEAAEIBAAMAAABkAAQBAAUAAEAA
Transfer-encoding: chunked
Upgrade: h2c
Accept: */*
Authorization: Basic **
Content-Type: text/xml; charset=UTF-8
SOAPAction: ""
User-Agent: Apache-CXF/3.6.1{code}
The server responds with {*}HTTP/1.1 101 Switching Protocols{*}.
*CXF 3.5.6*
I excluded CXF dependencies from Apache Camel and I downgraded it to 3.5.6
version and there wasn't this problem
{code:java}
.\X
POST /my-soap-service HTTP/1.1
Content-Type: text/xml; charset=UTF-8
Accept: */*
Authorization: Basic **
SOAPAction: ""
User-Agent: Apache-CXF/3.5.6
Cache-Control: no-cache
Pragma: no-cache
Host: my-host:8080
Connection: keep-alive
Transfer-Encoding: chunked {code}
> Upgrade, HTTP2-Settings - Apache-CXF/3.6.1
> --
>
> Key: CXF-8906
> URL: https://issues.apache.org/jira/browse/CXF-8906
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime, Soap Binding, Transports
>Affects Versions: 3.6.1
> Environment: Apache CXF 3.6.1
> Apache Camel 3.21.0
> Java 11
>Reporter: Giacomo Carnevale
>Priority: Major
> Fix For: 3.5.6
>
>
> Hi
> I am using Apache Camel CXF component to integrate soap services.
> Recently, I updated Apache Camel Version (3.20.x -> 3.21.0) and so Apache CXF
> version is changed (3.5.6 -> 3.6.1).
> *CXF 3.6.1*
> When I invoke SOAP service, by tcpdump I can see that CXF sets http headers
> '{*}Connection: Upgrade, HTTP2-Settings{*}', '{*}HTTP2-Settings:
> AAEAAEIBAAMAAABkAAQBAAUAAEAA{*}' and '{*}Upgrade: h2c{*}' but the
> connection is HTTP/1.1:
> {code:java}
> .o.91v..POST /my-soap-service HTTP/1.1
> Connection: Upgrade, HTTP2-Settings
> Host: myhost:8080
> HTTP2-Settings: AAEAAEIBAAMAAABkAAQBAAUAAEAA
> Transfer-encoding: chunked
> Upgrade: h2c
> Accept: */*
> Authorization: Basic **
> Content-Type: text/xml; charset=UTF-8
> SOAPAction: ""
> User-Agent: Apache-CXF/3.6.1{code}
>
>
> The server responds with {*}HTTP/1.1 101 Switching Protocols{*}.
> *CXF 3.5.6*
> I excluded CXF dependencies from Apache Camel and I downgraded it to 3.5.6
> version and there wasn't this problem
> {code:java}
> .\X
> POST /my-soap-service HTTP/1.1
> Content-Type: text/xml; charset=UTF-8
> Accept: */*
> Authorization: Basic **
> SOAPAction: ""
> User-Agent: Apache-CXF/3.5.6
> Cache-Control: no-cache
> Pragma: no-cache
> Host: my-host:8080
> Connection: keep-alive
> Transfer-Encoding: chunked {code}
>
>
--
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:
--
Description:
Get rid of EasyMock in favor of Mockito since it does require additional access
to sealed JDK internals for JDK-16 and above. Also, the EasyMock does not
support JDK-21 as of today.
{noformat}
Caused by: java.lang.IllegalArgumentException:
org.apache.cxf.io.CachedOutputStream$$$EasyMock$1 must be defined in the same
package as org.easymock.internal.ClassProxyFactory
at
org.easymock.bytebuddy.dynamic.loading.ClassInjector$UsingLookup.injectRaw(ClassInjector.java:1635)
at
org.easymock.bytebuddy.dynamic.loading.ClassInjector$AbstractBase.inject(ClassInjector.java:118)
at
org.easymock.bytebuddy.dynamic.loading.ClassLoadingStrategy$UsingLookup.load(ClassLoadingStrategy.java:519)
at
org.easymock.bytebuddy.dynamic.TypeResolutionStrategy$Passive.initialize(TypeResolutionStrategy.java:101)
at
org.easymock.bytebuddy.dynamic.DynamicType$Default$Unloaded.load(DynamicType.java:6317)
at
org.easymock.internal.ClassProxyFactory.lambda$createProxy$0(ClassProxyFactory.java:146)
at org.easymock.bytebuddy.TypeCache.findOrInsert(TypeCache.java:168)
... 34 more {noformat}
[X] ./core/pom.xml
[ ] ./integration/jca/pom.xml
[ ] ./rt/bindings/coloc/pom.xml
[X] ./rt/bindings/corba/pom.xml
[X] ./rt/bindings/soap/pom.xml
[X] ./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
[X] ./rt/frontend/jaxrs/pom.xml
[X] ./rt/frontend/jaxws/pom.xml
[ ] ./rt/frontend/js/pom.xml
[X] ./rt/management/pom.xml
[ ] ./rt/rs/client/pom.xml
[X] ./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
[X] ./rt/transports/http/pom.xml
[X] ./rt/transports/http-jetty/pom.xml
[ ] ./rt/transports/http-netty/netty-client/pom.xml
[ ] ./rt/transports/http-netty/netty-server/pom.xml
[X] ./rt/transports/http-undertow/pom.xml
[ ] ./rt/transports/jms/pom.xml
[X] ./rt/transports/websocket/pom.xml
[ ] ./rt/ws/addr/pom.xml
[X] ./rt/ws/policy/pom.xml
[ ] ./rt/ws/rm/pom.xml
[ ] ./rt/ws/security/pom.xml
[ ] ./rt/ws/transfer/pom.xml
[X] ./rt/wsdl/pom.xml
[ ] ./services/xkms/xkms-x509-handlers/pom.xml
[ ] ./services/xkms/xkms-x509-repo-ldap/pom.xml
was:
Get rid of EasyMock in favor of Mockito since it does require additional access
to sealed JDK internals for JDK-16 and above. Also, the EasyMock does not
support JDK-21 as of today.
{noformat}
Caused by: java.lang.IllegalArgumentException:
org.apache.cxf.io.CachedOutputStream$$$EasyMock$1 must be defined in the same
package as org.easymock.internal.ClassProxyFactory
at
org.easymock.bytebuddy.dynamic.loading.ClassInjector$UsingLookup.injectRaw(ClassInjector.java:1635)
at
org.easymock.bytebuddy.dynamic.loading.ClassInjector$AbstractBase.inject(ClassInjector.java:118)
at
org.easymock.bytebuddy.dynamic.loading.ClassLoadingStrategy$UsingLookup.load(ClassLoadingStrategy.java:519)
at
org.easymock.bytebuddy.dynamic.TypeResolutionStrategy$Passive.initialize(TypeResolutionStrategy.java:101)
at
org.easymock.bytebuddy.dynamic.DynamicType$Default$Unloaded.load(DynamicType.java:6317)
at
org.easymock.internal.ClassProxyFactory.lambda$createProxy$0(ClassProxyFactory.java:146)
at org.easymock.bytebuddy.TypeCache.findOrInsert(TypeCache.java:168)
... 34 more {noformat}
[X] ./core/pom.xml
[ ] ./integration/jca/pom.xml
[ ] ./rt/bindings/coloc/pom.xml
[ ] ./rt/bindings/corba/pom.xml
[X] ./rt/bindings/soap/pom.xml
[X] ./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
[X] ./rt/frontend/jaxrs/pom.xml
[X] ./rt/frontend/jaxws/pom.xml
[ ] ./rt/frontend/js/pom.xml
[X] ./rt/management/pom.xml
[ ] ./rt/rs/client/pom.xml
[X] ./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
[X] ./rt/transports/http/pom.xml
[X] ./rt/transports/http-jetty/pom.xml
[ ] ./rt/transports/http-netty/netty-client/pom.xml
[ ] ./rt/transports/http-netty/netty-server/pom.xml
[X] ./rt/transports/http-undertow/pom.xml
[ ] ./rt/transports/jms/pom.xml
[ ] ./rt/transports/websocket/pom.xml
[ ] ./rt/ws/addr/pom.xml
[X] ./rt/ws/policy/pom.xml
[ ] ./rt/ws/rm/pom.xml
[ ] ./rt/ws/security/pom.xml
[ ] ./rt/ws/transfer/pom.xml
[X] ./rt/
[jira] [Resolved] (CXF-8845) Get rid of EasyMock in cxf-rt-bindings-corba
[ https://issues.apache.org/jira/browse/CXF-8845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8845. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-bindings-corba > > > Key: CXF-8845 > URL: https://issues.apache.org/jira/browse/CXF-8845 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 3.6.2, 4.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CXF-8878) Get rid of EasyMock in cxf-rt-transports-http-netty-server
[ https://issues.apache.org/jira/browse/CXF-8878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8878: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-transports-http-netty-server > -- > > Key: CXF-8878 > URL: https://issues.apache.org/jira/browse/CXF-8878 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 3.6.2, 4.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CXF-8906) Upgrade, HTTP2-Settings - Apache-CXF/3.6.1
[
https://issues.apache.org/jira/browse/CXF-8906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko resolved CXF-8906.
---
Resolution: Duplicate
Duplicate of https://issues.apache.org/jira/browse/CXF-8896
> Upgrade, HTTP2-Settings - Apache-CXF/3.6.1
> --
>
> Key: CXF-8906
> URL: https://issues.apache.org/jira/browse/CXF-8906
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime, Soap Binding, Transports
>Affects Versions: 3.6.1
> Environment: Apache CXF 3.6.1
> Apache Camel 3.21.0
> Java 11
>Reporter: Giacomo Carnevale
>Priority: Major
> Fix For: 3.5.6
>
>
> Hi
> I am using Apache Camel CXF component to integrate soap services.
> Recently, I updated Apache Camel Version (3.20.x -> 3.21.0) and so Apache CXF
> version is changed (3.5.6 -> 3.6.1).
> *CXF 3.6.1*
> When I invoke SOAP service, by tcpdump I can see that CXF sets http headers
> '{*}Connection: Upgrade, HTTP2-Settings{*}', '{*}HTTP2-Settings:
> AAEAAEIBAAMAAABkAAQBAAUAAEAA{*}' and '{*}Upgrade: h2c{*}' but the
> connection is {*}HTTP/1.1{*}:
> {code:java}
> .o.91v..POST /my-soap-service HTTP/1.1
> Connection: Upgrade, HTTP2-Settings
> Host: myhost:8080
> HTTP2-Settings: AAEAAEIBAAMAAABkAAQBAAUAAEAA
> Transfer-encoding: chunked
> Upgrade: h2c
> Accept: */*
> Authorization: Basic **
> Content-Type: text/xml; charset=UTF-8
> SOAPAction: ""
> User-Agent: Apache-CXF/3.6.1{code}
>
>
> The server responds with {*}HTTP/1.1 101 Switching Protocols{*}.
> *CXF 3.5.6*
> I excluded CXF dependencies from Apache Camel and I downgraded it to 3.5.6
> version and there wasn't this problem
> {code:java}
> .\X
> POST /my-soap-service HTTP/1.1
> Content-Type: text/xml; charset=UTF-8
> Accept: */*
> Authorization: Basic **
> SOAPAction: ""
> User-Agent: Apache-CXF/3.5.6
> Cache-Control: no-cache
> Pragma: no-cache
> Host: my-host:8080
> Connection: keep-alive
> Transfer-Encoding: chunked {code}
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (CXF-8844) Get rid of EasyMock in cxf-rt-bindings-coloc
[ https://issues.apache.org/jira/browse/CXF-8844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8844: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-bindings-coloc > > > Key: CXF-8844 > URL: https://issues.apache.org/jira/browse/CXF-8844 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 3.6.2, 4.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
