[jira] [Created] (CXF-8927) org.apache.cxf.systest.jaxrs.JAXRSMultipartTest crashes the JVM (JDK21 only)
Andriy Redko created CXF-8927: - Summary: org.apache.cxf.systest.jaxrs.JAXRSMultipartTest crashes the JVM (JDK21 only) Key: CXF-8927 URL: https://issues.apache.org/jira/browse/CXF-8927 Project: CXF Issue Type: Test Reporter: Andriy Redko Assignee: Andriy Redko -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CXF-8925) Logging twice in case of faults happening after pre-stream phase in out-chain
[ https://issues.apache.org/jira/browse/CXF-8925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8925. --- Resolution: Fixed > Logging twice in case of faults happening after pre-stream phase in out-chain > - > > Key: CXF-8925 > URL: https://issues.apache.org/jira/browse/CXF-8925 > Project: CXF > Issue Type: Bug > Components: logging >Affects Versions: 3.5.6, 3.6.1, 4.0.2 > Environment: CXF server implementation using LoggingOutInterceptor on > both out chain and out fault chain (e.g. through LoggingFeature). >Reporter: Silwing >Priority: Minor > Fix For: 3.5.7, 3.6.2, 4.0.3 > > > When using the LoggingOutInterceptor in a server context with the interceptor > added to the Out Chain and the Out Fault Chain events will be created and > sent twice if faults occur after the phase the LoggingOutIntercept is bound > to. > The cause of the issue is that handleMessage is called twice; once during the > out chain and once during the out fault chain. This wraps the message content > OutputStream twice in LoggingOutputStreams and adds two callbacks both > creating logging events and sending them to the LogEventSender. > When combined with the StaxOutInterceptor it furthermore causes one of the > events to have an empty payload. This is due to the StaxOutInterceptor > wrapping the LoggingOutputStream created during the out chain, and *not* the > LoggingOutputStream created during the out fault chain. Meaning content is > only written to the inner LoggingOutputStream and not to the outer one. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8925) Logging twice in case of faults happening after pre-stream phase in out-chain
[ https://issues.apache.org/jira/browse/CXF-8925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8925: -- Fix Version/s: 3.5.7 3.6.2 4.0.3 > Logging twice in case of faults happening after pre-stream phase in out-chain > - > > Key: CXF-8925 > URL: https://issues.apache.org/jira/browse/CXF-8925 > Project: CXF > Issue Type: Bug > Components: logging >Affects Versions: 3.5.6, 3.6.1, 4.0.2 > Environment: CXF server implementation using LoggingOutInterceptor on > both out chain and out fault chain (e.g. through LoggingFeature). >Reporter: Silwing >Priority: Minor > Fix For: 3.5.7, 3.6.2, 4.0.3 > > > When using the LoggingOutInterceptor in a server context with the interceptor > added to the Out Chain and the Out Fault Chain events will be created and > sent twice if faults occur after the phase the LoggingOutIntercept is bound > to. > The cause of the issue is that handleMessage is called twice; once during the > out chain and once during the out fault chain. This wraps the message content > OutputStream twice in LoggingOutputStreams and adds two callbacks both > creating logging events and sending them to the LogEventSender. > When combined with the StaxOutInterceptor it furthermore causes one of the > events to have an empty payload. This is due to the StaxOutInterceptor > wrapping the LoggingOutputStream created during the out chain, and *not* the > LoggingOutputStream created during the out fault chain. Meaning content is > only written to the inner LoggingOutputStream and not to the outer one. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8671) Support Jakarta EE 10
[ https://issues.apache.org/jira/browse/CXF-8671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8671: -- Description: Support Jakarta EE 10 Jakarta EE 10 has Landed - [https://jakartaee-ambassadors.io/2022/09/22/jakarta-ee-10-released/] [https://jakarta.ee/release/10/] [https://www.infoq.com/news/2023/01/glassfish-delivers-support-jdk17/] Specs: * Jakarta Activation 2.1* * Jakarta Authentication 3.0* * Jakarta Authorization 2.1* * Jakarta Batch 2.1* * Jakarta Bean Validation 3.0 * Jakarta Common Annotations 2.1* * Jakarta Concurrency 3.0* * Jakarta Connectors 2.1* * Jakarta Contexts and Dependency Injection 4.0* * Jakarta Debugging Support for Other Languages 2.0 * Jakarta Dependency Injection 2.0 * Jakarta Enterprise Beans 4.0 (except for Jakarta Enterprise Beans entity beans and associated Jakarta Enterprise Beans QL, and embedded container, which have been made removed) * Jakarta Expression Language 5.0* * Jakarta Interceptors 2.1* * Jakarta JSON Processing 2.1* * Jakarta JSON Binding 3.0* * Jakarta Mail 2.1* * Jakarta Managed Beans 2.0 * Jakarta Messaging 3.1* * Jakarta Persistence 3.1* * Jakarta RESTful Web Services 3.1* * Jakarta Security 3.0* * Jakarta Servlet 6.0* * Jakarta Server Faces 4.0* * Jakarta Server Pages 3.1* * Jakarta Standard Tag Library 3.0* * Jakarta Transactions 2.0 * Jakarta WebSocket 2.1* * Jakarta Enterprise Beans 3.2 and earlier entity beans and associated Jakarta Enterprise Beans QL * Jakarta Enterprise Beans 2.x API group * Jakarta Enterprise Web Services 2.0 * Jakarta SOAP with Attachments 3.0* * Jakarta XML Web Services 4.0* * Jakarta XML Binding 4.0* Rest Client TCK update: - [https://github.com/eclipse/microprofile-rest-client/pull/352] Updates required: - Undertow 2.3.x - Jetty 12 ([https://github.com/eclipse/jetty.project/releases/tag/jetty-12.0.0.beta0]) - Hibernate Validator 8 ([https://hibernate.org/validator/releases/8.0/)] - Hibernate 6.3 (https://in.relation.to/2023/08/31/orm-630/) - Weld 5 ([https://weld.cdi-spec.org/news/2022/04/29/weld-500Final/]) - Spring Boot 3.1 ([https://github.com/spring-projects/spring-boot/releases/tag/v3.1.0]) - Spring Security 6.1 ([https://github.com/spring-projects/spring-security/releases/tag/6.1.0]) - Micrometer 1.11 ([https://github.com/micrometer-metrics/micrometer/releases/tag/v1.11.0|https://github.com/micrometer-metrics/micrometer/releases/tag/v1.11.0-M1]) - Micrometer Tracing 1.1 ([https://github.com/micrometer-metrics/tracing/releases/tag/v1.1.4)] - Spring LDAP 3.1 ([https://github.com/spring-projects/spring-ldap/releases/tag/3.1.0)] Microprofile 6.0 ([https://download.eclipse.org/microprofile/microprofile-6.0/microprofile-spec-6.0.html),] aligned with JakartaEE 10 core profile: - Microprofile OpenAPI 3.1 ([https://github.com/eclipse/microprofile-open-api/releases/tag/3.1]) - Angus Mail ([https://github.com/eclipse-ee4j/angus-mail/releases/tag/2.0.1]) - [https://github.com/arquillian/arquillian-container-weld/releases/tag/3.0.2.Final] was: Support Jakarta EE 10 Jakarta EE 10 has Landed - [https://jakartaee-ambassadors.io/2022/09/22/jakarta-ee-10-released/] [https://jakarta.ee/release/10/] [https://www.infoq.com/news/2023/01/glassfish-delivers-support-jdk17/] Specs: * Jakarta Activation 2.1* * Jakarta Authentication 3.0* * Jakarta Authorization 2.1* * Jakarta Batch 2.1* * Jakarta Bean Validation 3.0 * Jakarta Common Annotations 2.1* * Jakarta Concurrency 3.0* * Jakarta Connectors 2.1* * Jakarta Contexts and Dependency Injection 4.0* * Jakarta Debugging Support for Other Languages 2.0 * Jakarta Dependency Injection 2.0 * Jakarta Enterprise Beans 4.0 (except for Jakarta Enterprise Beans entity beans and associated Jakarta Enterprise Beans QL, and embedded container, which have been made removed) * Jakarta Expression Language 5.0* * Jakarta Interceptors 2.1* * Jakarta JSON Processing 2.1* * Jakarta JSON Binding 3.0* * Jakarta Mail 2.1* * Jakarta Managed Beans 2.0 * Jakarta Messaging 3.1* * Jakarta Persistence 3.1* * Jakarta RESTful Web Services 3.1* * Jakarta Security 3.0* * Jakarta Servlet 6.0* * Jakarta Server Faces 4.0* * Jakarta Server Pages 3.1* * Jakarta Standard Tag Library 3.0* * Jakarta Transactions 2.0 * Jakarta WebSocket 2.1* * Jakarta Enterprise Beans 3.2 and earlier entity beans and associated Jakarta Enterprise Beans QL * Jakarta Enterprise Beans 2.x API group * Jakarta Enterprise Web Services 2.0 * Jakarta SOAP with Attachments 3.0* * Jakarta XML Web Services 4.0* * Jakarta XML Binding 4.0* Rest Client TCK update: - [https://github.com/eclipse/microprofile-rest-client/pull/352] Updates required: - Undertow 2.3.x - Jetty 12 ([https://github.com/eclipse/jetty.project/releases/tag/jetty-12.0.0.beta0]) - Hibernate
[jira] [Resolved] (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 resolved CXF-8549.
---
Resolution: Fixed
> Get rid of EasyMock
>
>
> Key: CXF-8549
> URL: https://issues.apache.org/jira/browse/CXF-8549
> Project: CXF
> Issue Type: Task
>Affects Versions: 4.0.1, 3.6.1
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.6.2, 4.0.3
>
>
> 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
> [X] ./integration/jca/pom.xml
> [X] ./rt/bindings/coloc/pom.xml
> [X] ./rt/bindings/corba/pom.xml
> [X] ./rt/bindings/soap/pom.xml
> [X] ./rt/databinding/aegis/pom.xml
> [X] ./rt/databinding/jaxb/pom.xml
> [X] ./rt/features/clustering/pom.xml
> [X] ./rt/features/logging/pom.xml
> [X] ./rt/features/throttling/pom.xml
> [X] ./rt/frontend/jaxrs/pom.xml
> [X] ./rt/frontend/jaxws/pom.xml
> [X] ./rt/frontend/js/pom.xml
> [X] ./rt/management/pom.xml
> [X] ./rt/rs/client/pom.xml
> [X] ./rt/rs/description/pom.xml
> [X] ./rt/rs/extensions/providers/pom.xml
> [X] ./rt/rs/extensions/search/pom.xml
> [X] ./rt/rs/microprofile-client/pom.xml
> [X] ./rt/rs/security/oauth-parent/oauth2/pom.xml
> [X] ./rt/rs/security/oauth-parent/oauth2-saml/pom.xml
> [X] ./rt/rs/security/sso/oidc/pom.xml
> [X] ./rt/transports/http/pom.xml
> [X] ./rt/transports/http-jetty/pom.xml
> [X] ./rt/transports/http-netty/netty-client/pom.xml
> [X] ./rt/transports/http-netty/netty-server/pom.xml
> [X] ./rt/transports/http-undertow/pom.xml
> [X] ./rt/transports/jms/pom.xml
> [X] ./rt/transports/websocket/pom.xml
> [X] ./rt/ws/addr/pom.xml
> [X] ./rt/ws/policy/pom.xml
> [X] ./rt/ws/rm/pom.xml
> [X] ./rt/ws/security/pom.xml
> [X] ./rt/ws/transfer/pom.xml
> [X] ./rt/wsdl/pom.xml
> [X] ./services/xkms/xkms-x509-handlers/pom.xml
> [X] ./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.2
4.0.3
> Get rid of EasyMock
>
>
> Key: CXF-8549
> URL: https://issues.apache.org/jira/browse/CXF-8549
> Project: CXF
> Issue Type: Task
>Affects Versions: 4.0.1, 3.6.1
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.6.2, 4.0.3
>
>
> 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
> [X] ./integration/jca/pom.xml
> [X] ./rt/bindings/coloc/pom.xml
> [X] ./rt/bindings/corba/pom.xml
> [X] ./rt/bindings/soap/pom.xml
> [X] ./rt/databinding/aegis/pom.xml
> [X] ./rt/databinding/jaxb/pom.xml
> [X] ./rt/features/clustering/pom.xml
> [X] ./rt/features/logging/pom.xml
> [X] ./rt/features/throttling/pom.xml
> [X] ./rt/frontend/jaxrs/pom.xml
> [X] ./rt/frontend/jaxws/pom.xml
> [X] ./rt/frontend/js/pom.xml
> [X] ./rt/management/pom.xml
> [X] ./rt/rs/client/pom.xml
> [X] ./rt/rs/description/pom.xml
> [X] ./rt/rs/extensions/providers/pom.xml
> [X] ./rt/rs/extensions/search/pom.xml
> [X] ./rt/rs/microprofile-client/pom.xml
> [X] ./rt/rs/security/oauth-parent/oauth2/pom.xml
> [X] ./rt/rs/security/oauth-parent/oauth2-saml/pom.xml
> [X] ./rt/rs/security/sso/oidc/pom.xml
> [X] ./rt/transports/http/pom.xml
> [X] ./rt/transports/http-jetty/pom.xml
> [X] ./rt/transports/http-netty/netty-client/pom.xml
> [X] ./rt/transports/http-netty/netty-server/pom.xml
> [X] ./rt/transports/http-undertow/pom.xml
> [X] ./rt/transports/jms/pom.xml
> [X] ./rt/transports/websocket/pom.xml
> [X] ./rt/ws/addr/pom.xml
> [X] ./rt/ws/policy/pom.xml
> [X] ./rt/ws/rm/pom.xml
> [X] ./rt/ws/security/pom.xml
> [X] ./rt/ws/transfer/pom.xml
> [X] ./rt/wsdl/pom.xml
> [X] ./services/xkms/xkms-x509-handlers/pom.xml
> [X] ./services/xkms/xkms-x509-repo-ldap/pom.xml
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CXF-8921) Get rid of EasyMock in cxf-rt-rs-service-description-swagger
[ https://issues.apache.org/jira/browse/CXF-8921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8921. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-rs-service-description-swagger > > > Key: CXF-8921 > URL: https://issues.apache.org/jira/browse/CXF-8921 > Project: CXF > Issue Type: Sub-task >Affects Versions: 3.6.1 >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 3.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CXF-8914) No content-length header after upgrade CXF from 3.5.6 to 3.6.1
[ https://issues.apache.org/jira/browse/CXF-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8914. --- Fix Version/s: 3.6.2 4.0.3 Resolution: Workaround > No content-length header after upgrade CXF from 3.5.6 to 3.6.1 > -- > > Key: CXF-8914 > URL: https://issues.apache.org/jira/browse/CXF-8914 > Project: CXF > Issue Type: Bug >Affects Versions: 3.6.1 > Environment: SpringBoot 2.7.13 >Reporter: Stephan Näcker >Priority: Major > Fix For: 3.6.2, 4.0.3 > > > After updating the CXF dependency in our application from 3.5.6 to 3.6.1 it > does not add a content-length header anymore, when doing a multipart request > for a file upload. > I didn't find any information, how to let CXF set the header. Is it just > dependent of chunking? > Actually the application sets "allow chunking" to false. But I'm not sure, > how I can test, if this really works. > Thanks in advance for your help. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8914) No content-length header after upgrade CXF from 3.5.6 to 3.6.1
[ https://issues.apache.org/jira/browse/CXF-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17761090#comment-17761090 ] Andriy Redko commented on CXF-8914: --- Hey [~stephan.naecker] , in the upcoming 3.6.2 / 4.0.3 releases, a new Bus / system property "org.apache.cxf.transport.http.forceURLConnection" would allow to fallback to the old HttpConduit, see please [https://github.com/apache/cxf/commit/3d70de80fb60b74040c0214fc6a28774362556e4.] > No content-length header after upgrade CXF from 3.5.6 to 3.6.1 > -- > > Key: CXF-8914 > URL: https://issues.apache.org/jira/browse/CXF-8914 > Project: CXF > Issue Type: Bug >Affects Versions: 3.6.1 > Environment: SpringBoot 2.7.13 >Reporter: Stephan Näcker >Priority: Major > > After updating the CXF dependency in our application from 3.5.6 to 3.6.1 it > does not add a content-length header anymore, when doing a multipart request > for a file upload. > I didn't find any information, how to let CXF set the header. Is it just > dependent of chunking? > Actually the application sets "allow chunking" to false. But I'm not sure, > how I can test, if this really works. > Thanks in advance for your help. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8921) Get rid of EasyMock in cxf-rt-rs-service-description-swagger
[ https://issues.apache.org/jira/browse/CXF-8921?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8921: -- Summary: Get rid of EasyMock in cxf-rt-rs-service-description-swagger (was: Get rid of EasyMock on cxf-rt-rs-service-description-swagger) > Get rid of EasyMock in cxf-rt-rs-service-description-swagger > > > Key: CXF-8921 > URL: https://issues.apache.org/jira/browse/CXF-8921 > Project: CXF > Issue Type: Sub-task >Affects Versions: 3.6.1 >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 3.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CXF-8921) Get rid of EasyMock on cxf-rt-rs-service-description-swagger
Andriy Redko created CXF-8921: - Summary: Get rid of EasyMock on cxf-rt-rs-service-description-swagger Key: CXF-8921 URL: https://issues.apache.org/jira/browse/CXF-8921 Project: CXF Issue Type: Sub-task Affects Versions: 3.6.1 Reporter: Andriy Redko Assignee: Andriy Redko Fix For: 3.6.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8407) Incorporate changes caused by JEP-396 integration into JDK-16+
[
https://issues.apache.org/jira/browse/CXF-8407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko updated CXF-8407:
--
Description:
JEP-396 introduces stronger encapsulation of JDK internals by default. In CXF,
we are using a number of tricks to access JDK internals, including but not
limited to:
* -AutomaticWorkQueueImpl uses private ThreadPoolExecutor::addWorker: needs
--add-opens java.base/java.util.concurrent=ALL-UNNAMED-
* -EasyMock: needs --add-opens java.base/java.lang=ALL-UNNAMED- (fixed in
EasyMock 5.0.1 by moving off to ByteBuddy)
* CgLib (Spring AOP): needs --add-opens java.base/java.lang=ALL-UNNAMED
{noformat}
Caused by: org.springframework.cglib.core.CodeGenerationException:
java.lang.reflect.InaccessibleObjectException-->Unable to make protected final
java.lang.Class
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
throws java.lang.ClassFormatError accessible: module java.base does not "opens
java.lang" to unnamed module @1e67b872
at
org.springframework.cglib.core.ReflectUtils.defineClass(ReflectUtils.java:549)
{noformat}
* -ImportRepairTest uses XSImplementationImpl: --add-exports
java.xml/com.sun.org.apache.xerces.internal.impl.xs=ALL-UNNAMED --add-exports
java.xml/com.sun.org.apache.xerces.internal.impl.xs.util=ALL-UNNAMED-
* -ReferencingAuthenticator (method tryWith): needs --add-opens
java.base/java.net=ALL-UNNAMED-
* -stax.WriterTest: needs- -add-opens
java.xml/com.sun.org.apache.xerces.internal.jaxp=ALL-UNNAMED-
* {color:#172b4d}-johnzon-jsonb: needs --add-opens
java.base/java.util=ALL-UNNAMED-{color}
* -*SOAPRpcLitClientTypeTest* with xercesImpl: needs --add-opens
java.xml/javax.xml.namespace=ALL-UNNAMED (see please
[https://github.com/javaee/jaxb-v2/issues/1184])-
* .{-}*JAXRSLDAPUserTest*{-}: (fixed by CXF-8809)
- -apacheds needs --add-opens java.base/sun.security.x509=ALL-UNNAMED
{}add-opens java.base/sun.security.util=ALL-UNNAMED-
- -org.springframework.ldap needs -add-opens
java.naming/com.sun.jndi.ldap=ALL-UNNAMED- (fixed in 2.3.4.RELEASE)
* -*JsFrontEndServletTest* & {*}JSClientServerTest{*}: need --add-opens
java.xml/com.sun.org.apache.xerces.internal.dom=ALL-UNNAMED (saaj-impl 1.5.3
SOAPDocumentImpl::createDocument() instantiates
`com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderFactoryImpl`)-
* *JAXRSClientServerBookTest* & {*}JAXRSHttpsBookTest{*}: need --add-opens
java.base/java.net=ALL-UNNAMED --add-opens
java.base/sun.net.[www.protocol.https=ALL-UNNAMED|http://www.protocol.https=all-unnamed/]
(setting custom HTTP method fe RETRIEVE in
URLConnectionHTTPConduit::setupConnection using reflection)
We should migrate from using those to the means provided by standard library.
[1] [https://openjdk.java.net/jeps/396]
[2] [https://cr.openjdk.java.net/~mr/jigsaw/jdk8-packages-denied-by-default]
was:
JEP-396 introduces stronger encapsulation of JDK internals by default. In CXF,
we are using a number of tricks to access JDK internals, including but not
limited to:
* -AutomaticWorkQueueImpl uses private ThreadPoolExecutor::addWorker: needs
--add-opens java.base/java.util.concurrent=ALL-UNNAMED-
* -EasyMock: needs --add-opens java.base/java.lang=ALL-UNNAMED- (fixed in
EasyMock 5.0.1 by moving off to ByteBuddy)
* CgLib (Spring AOP): needs --add-opens java.base/java.lang=ALL-UNNAMED
{noformat}
Caused by: org.springframework.cglib.core.CodeGenerationException:
java.lang.reflect.InaccessibleObjectException-->Unable to make protected final
java.lang.Class
java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int,java.security.ProtectionDomain)
throws java.lang.ClassFormatError accessible: module java.base does not "opens
java.lang" to unnamed module @1e67b872
at
org.springframework.cglib.core.ReflectUtils.defineClass(ReflectUtils.java:549)
{noformat}
* -ImportRepairTest uses XSImplementationImpl: --add-exports
java.xml/com.sun.org.apache.xerces.internal.impl.xs=ALL-UNNAMED --add-exports
java.xml/com.sun.org.apache.xerces.internal.impl.xs.util=ALL-UNNAMED-
* -ReferencingAuthenticator (method tryWith): needs --add-opens
java.base/java.net=ALL-UNNAMED-
* -stax.WriterTest: needs- -add-opens
java.xml/com.sun.org.apache.xerces.internal.jaxp=ALL-UNNAMED-
* {color:#172b4d}-johnzon-jsonb: needs --add-opens
java.base/java.util=ALL-UNNAMED-{color}
* *SOAPRpcLitClientTypeTest* with xercesImpl: needs --add-opens
java.xml/javax.xml.namespace=ALL-UNNAMED (see please
[https://github.com/javaee/jaxb-v2/issues/1184])
* .{-}*JAXRSLDAPUserTest*{-}: (fixed by CXF-8809)
- -apacheds needs --add-opens java.base/sun.security.x509=ALL-UNNAMED
{}add-opens java.base/sun.security.util=ALL-UNNAMED-
- -org.springframework.ldap needs -add-opens
java.naming/com.sun.jndi.ldap=ALL-UNNAMED- (fixed in 2.3.4.RELEASE)
* *JsFrontEndServletTest* & {*}JSClientServerTest{*}: need --add-opens
[jira] [Resolved] (CXF-8920) Can't filter when collection has attribute of type LocalDate or LocalDateTime
[ https://issues.apache.org/jira/browse/CXF-8920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8920. --- Resolution: Fixed > Can't filter when collection has attribute of type LocalDate or LocalDateTime > - > > Key: CXF-8920 > URL: https://issues.apache.org/jira/browse/CXF-8920 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 3.6.1, 4.0.2 >Reporter: Andrei Bastun >Priority: Major > Fix For: 3.5.7, 3.6.2, 4.0.3 > > > When trying to filter using fiql language : > filter:"collection.startDate=gt=2014-11-04" > with startDate is of type *LocalDate.* > We get the exception *"Cannot convert String Value to a value of class > LocalDate"* > > It is the same as in CXF-8659 but for collection properties (with dot) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CXF-8853) Get rid of EasyMock in cxf-services-xkms-x509-handlers
[ https://issues.apache.org/jira/browse/CXF-8853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8853. --- Resolution: Fixed > Get rid of EasyMock in cxf-services-xkms-x509-handlers > -- > > Key: CXF-8853 > URL: https://issues.apache.org/jira/browse/CXF-8853 > 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] [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
[X] ./integration/jca/pom.xml
[X] ./rt/bindings/coloc/pom.xml
[X] ./rt/bindings/corba/pom.xml
[X] ./rt/bindings/soap/pom.xml
[X] ./rt/databinding/aegis/pom.xml
[X] ./rt/databinding/jaxb/pom.xml
[X] ./rt/features/clustering/pom.xml
[X] ./rt/features/logging/pom.xml
[X] ./rt/features/throttling/pom.xml
[X] ./rt/frontend/jaxrs/pom.xml
[X] ./rt/frontend/jaxws/pom.xml
[X] ./rt/frontend/js/pom.xml
[X] ./rt/management/pom.xml
[X] ./rt/rs/client/pom.xml
[X] ./rt/rs/description/pom.xml
[X] ./rt/rs/extensions/providers/pom.xml
[X] ./rt/rs/extensions/search/pom.xml
[X] ./rt/rs/microprofile-client/pom.xml
[X] ./rt/rs/security/oauth-parent/oauth2/pom.xml
[X] ./rt/rs/security/oauth-parent/oauth2-saml/pom.xml
[X] ./rt/rs/security/sso/oidc/pom.xml
[X] ./rt/transports/http/pom.xml
[X] ./rt/transports/http-jetty/pom.xml
[X] ./rt/transports/http-netty/netty-client/pom.xml
[X] ./rt/transports/http-netty/netty-server/pom.xml
[X] ./rt/transports/http-undertow/pom.xml
[X] ./rt/transports/jms/pom.xml
[X] ./rt/transports/websocket/pom.xml
[X] ./rt/ws/addr/pom.xml
[X] ./rt/ws/policy/pom.xml
[X] ./rt/ws/rm/pom.xml
[X] ./rt/ws/security/pom.xml
[X] ./rt/ws/transfer/pom.xml
[X] ./rt/wsdl/pom.xml
[X] ./services/xkms/xkms-x509-handlers/pom.xml
[X] ./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
[X] ./integration/jca/pom.xml
[X] ./rt/bindings/coloc/pom.xml
[X] ./rt/bindings/corba/pom.xml
[X] ./rt/bindings/soap/pom.xml
[X] ./rt/databinding/aegis/pom.xml
[X] ./rt/databinding/jaxb/pom.xml
[X] ./rt/features/clustering/pom.xml
[X] ./rt/features/logging/pom.xml
[X] ./rt/features/throttling/pom.xml
[X] ./rt/frontend/jaxrs/pom.xml
[X] ./rt/frontend/jaxws/pom.xml
[X] ./rt/frontend/js/pom.xml
[X] ./rt/management/pom.xml
[ ] ./rt/rs/client/pom.xml
[X] ./rt/rs/description/pom.xml
[X] ./rt/rs/extensions/providers/pom.xml
[X] ./rt/rs/extensions/search/pom.xml
[X] ./rt/rs/microprofile-client/pom.xml
[X] ./rt/rs/security/oauth-parent/oauth2/pom.xml
[X] ./rt/rs/security/oauth-parent/oauth2-saml/pom.xml
[X] ./rt/rs/security/sso/oidc/pom.xml
[X] ./rt/transports/http/pom.xml
[X] ./rt/transports/http-jetty/pom.xml
[X] ./rt/transports/http-netty/netty-client/pom.xml
[X] ./rt/transports/http-netty/netty-server/pom.xml
[X] ./rt/transports/http-undertow/pom.xml
[X] ./rt/transports/jms/pom.xml
[X] ./rt/transports/websocket/pom.xml
[X] ./rt/ws/addr/pom.xml
[X] ./rt/ws/policy/pom.xml
[X] ./rt/ws/rm/pom.xml
[X] ./rt/ws/security/pom.xml
[X] ./rt/ws/transfer/pom.xml
[X]
[jira] [Resolved] (CXF-8457) Provide OpenTelemetry support
[ https://issues.apache.org/jira/browse/CXF-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8457. --- Resolution: Fixed > Provide OpenTelemetry support > - > > Key: CXF-8457 > URL: https://issues.apache.org/jira/browse/CXF-8457 > Project: CXF > Issue Type: Improvement > Components: Tracing >Reporter: Andriy Redko >Priority: Major > Fix For: 3.5.7, 3.6.2, 4.0.3 > > > The OpenTelemetry [1] is getting matured [2] and adopted widely. Although > shims exists, it would be good to support it natively along with Zipkin and > OpenTracing (which is deprecated [3]). > [1] [https://github.com/open-telemetry/opentelemetry-java] > [2] [https://github.com/open-telemetry/opentelemetry-java/releases/tag/v1.2.0] > [3] > [https://medium.com/opentracing/opentracing-has-been-archived-fb2848cfef67] > > Documentation: > * [https://cwiki.apache.org/confluence/display/CXF20DOC/Using+OpenTelemetry] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8920) Can't filter when collection has attribute of type LocalDate or LocalDateTime
[ https://issues.apache.org/jira/browse/CXF-8920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8920: -- Fix Version/s: 3.5.7 3.6.2 4.0.3 > Can't filter when collection has attribute of type LocalDate or LocalDateTime > - > > Key: CXF-8920 > URL: https://issues.apache.org/jira/browse/CXF-8920 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 3.6.1, 4.0.2 >Reporter: Andrei Bastun >Priority: Major > Fix For: 3.5.7, 3.6.2, 4.0.3 > > > When trying to filter using fiql language : > filter:"collection.startDate=gt=2014-11-04" > with startDate is of type *LocalDate.* > We get the exception *"Cannot convert String Value to a value of class > LocalDate"* > > It is the same as in CXF-8659 but for collection properties (with dot) -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CXF-8867) Get rid of EasyMock in cxf-rt-rs-client
[ https://issues.apache.org/jira/browse/CXF-8867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8867. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-rs-client > --- > > Key: CXF-8867 > URL: https://issues.apache.org/jira/browse/CXF-8867 > 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-8868) Get rid of EasyMock in cxf-rt-rs-extension-providers
[ https://issues.apache.org/jira/browse/CXF-8868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8868. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-rs-extension-providers > > > Key: CXF-8868 > URL: https://issues.apache.org/jira/browse/CXF-8868 > 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] [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
[X] ./integration/jca/pom.xml
[X] ./rt/bindings/coloc/pom.xml
[X] ./rt/bindings/corba/pom.xml
[X] ./rt/bindings/soap/pom.xml
[X] ./rt/databinding/aegis/pom.xml
[X] ./rt/databinding/jaxb/pom.xml
[X] ./rt/features/clustering/pom.xml
[X] ./rt/features/logging/pom.xml
[X] ./rt/features/throttling/pom.xml
[X] ./rt/frontend/jaxrs/pom.xml
[X] ./rt/frontend/jaxws/pom.xml
[X] ./rt/frontend/js/pom.xml
[X] ./rt/management/pom.xml
[ ] ./rt/rs/client/pom.xml
[X] ./rt/rs/description/pom.xml
[X] ./rt/rs/extensions/providers/pom.xml
[X] ./rt/rs/extensions/search/pom.xml
[X] ./rt/rs/microprofile-client/pom.xml
[X] ./rt/rs/security/oauth-parent/oauth2/pom.xml
[X] ./rt/rs/security/oauth-parent/oauth2-saml/pom.xml
[X] ./rt/rs/security/sso/oidc/pom.xml
[X] ./rt/transports/http/pom.xml
[X] ./rt/transports/http-jetty/pom.xml
[X] ./rt/transports/http-netty/netty-client/pom.xml
[X] ./rt/transports/http-netty/netty-server/pom.xml
[X] ./rt/transports/http-undertow/pom.xml
[X] ./rt/transports/jms/pom.xml
[X] ./rt/transports/websocket/pom.xml
[X] ./rt/ws/addr/pom.xml
[X] ./rt/ws/policy/pom.xml
[X] ./rt/ws/rm/pom.xml
[X] ./rt/ws/security/pom.xml
[X] ./rt/ws/transfer/pom.xml
[X] ./rt/wsdl/pom.xml
[X] ./services/xkms/xkms-x509-handlers/pom.xml
[X] ./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
[X] ./integration/jca/pom.xml
[X] ./rt/bindings/coloc/pom.xml
[X] ./rt/bindings/corba/pom.xml
[X] ./rt/bindings/soap/pom.xml
[X] ./rt/databinding/aegis/pom.xml
[X] ./rt/databinding/jaxb/pom.xml
[X] ./rt/features/clustering/pom.xml
[X] ./rt/features/logging/pom.xml
[X] ./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
[X] ./rt/rs/microprofile-client/pom.xml
[X] ./rt/rs/security/oauth-parent/oauth2/pom.xml
[X] ./rt/rs/security/oauth-parent/oauth2-saml/pom.xml
[X] ./rt/rs/security/sso/oidc/pom.xml
[X] ./rt/transports/http/pom.xml
[X] ./rt/transports/http-jetty/pom.xml
[X] ./rt/transports/http-netty/netty-client/pom.xml
[X] ./rt/transports/http-netty/netty-server/pom.xml
[X] ./rt/transports/http-undertow/pom.xml
[X] ./rt/transports/jms/pom.xml
[X] ./rt/transports/websocket/pom.xml
[X] ./rt/ws/addr/pom.xml
[X] ./rt/ws/policy/pom.xml
[ ] ./rt/ws/rm/pom.xml
[ ] ./rt/ws/security/pom.xml
[X] ./rt/ws/transfer/pom.xml
[X]
[jira] [Resolved] (CXF-8852) Get rid of EasyMock in cxf-services-xkms-x509-repo-ldap
[ https://issues.apache.org/jira/browse/CXF-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8852. --- Resolution: Fixed > Get rid of EasyMock in cxf-services-xkms-x509-repo-ldap > --- > > Key: CXF-8852 > URL: https://issues.apache.org/jira/browse/CXF-8852 > 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-8871) Get rid of EasyMock in cxf-rt-rs-mp-client
[ https://issues.apache.org/jira/browse/CXF-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8871. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-rs-mp-client > -- > > Key: CXF-8871 > URL: https://issues.apache.org/jira/browse/CXF-8871 > 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] [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
[X] ./integration/jca/pom.xml
[X] ./rt/bindings/coloc/pom.xml
[X] ./rt/bindings/corba/pom.xml
[X] ./rt/bindings/soap/pom.xml
[X] ./rt/databinding/aegis/pom.xml
[X] ./rt/databinding/jaxb/pom.xml
[X] ./rt/features/clustering/pom.xml
[X] ./rt/features/logging/pom.xml
[X] ./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
[X] ./rt/rs/microprofile-client/pom.xml
[X] ./rt/rs/security/oauth-parent/oauth2/pom.xml
[X] ./rt/rs/security/oauth-parent/oauth2-saml/pom.xml
[X] ./rt/rs/security/sso/oidc/pom.xml
[X] ./rt/transports/http/pom.xml
[X] ./rt/transports/http-jetty/pom.xml
[X] ./rt/transports/http-netty/netty-client/pom.xml
[X] ./rt/transports/http-netty/netty-server/pom.xml
[X] ./rt/transports/http-undertow/pom.xml
[X] ./rt/transports/jms/pom.xml
[X] ./rt/transports/websocket/pom.xml
[X] ./rt/ws/addr/pom.xml
[X] ./rt/ws/policy/pom.xml
[ ] ./rt/ws/rm/pom.xml
[ ] ./rt/ws/security/pom.xml
[X] ./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
[X] ./integration/jca/pom.xml
[X] ./rt/bindings/coloc/pom.xml
[X] ./rt/bindings/corba/pom.xml
[X] ./rt/bindings/soap/pom.xml
[X] ./rt/databinding/aegis/pom.xml
[X] ./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
[X] ./rt/rs/microprofile-client/pom.xml
[X] ./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
[X] ./rt/transports/http-netty/netty-client/pom.xml
[X] ./rt/transports/http-netty/netty-server/pom.xml
[X] ./rt/transports/http-undertow/pom.xml
[X] ./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]
[jira] [Updated] (CXF-8853) Get rid of EasyMock in cxf-services-xkms-x509-handlers
[ https://issues.apache.org/jira/browse/CXF-8853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8853: -- Summary: Get rid of EasyMock in cxf-services-xkms-x509-handlers (was: Get rid of EasyMock in xkms-x509-handlers) > Get rid of EasyMock in cxf-services-xkms-x509-handlers > -- > > Key: CXF-8853 > URL: https://issues.apache.org/jira/browse/CXF-8853 > 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] [Updated] (CXF-8853) Get rid of EasyMock in xkms-x509-handlers
[ https://issues.apache.org/jira/browse/CXF-8853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8853: -- Summary: Get rid of EasyMock in xkms-x509-handlers (was: Get rid of EasyMock in org.apache.cxf.services.xkms) > Get rid of EasyMock in xkms-x509-handlers > - > > Key: CXF-8853 > URL: https://issues.apache.org/jira/browse/CXF-8853 > 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-8850) Get rid of EasyMock in cxf-rt-features-logging
[ https://issues.apache.org/jira/browse/CXF-8850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8850. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-features-logging > -- > > Key: CXF-8850 > URL: https://issues.apache.org/jira/browse/CXF-8850 > 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-8851) Get rid of EasyMock in cxf-rt-features-throttling
[ https://issues.apache.org/jira/browse/CXF-8851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8851. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-features-throttling > - > > Key: CXF-8851 > URL: https://issues.apache.org/jira/browse/CXF-8851 > 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-8849) Get rid of EasyMock in cxf-rt-features-clustering
[ https://issues.apache.org/jira/browse/CXF-8849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8849. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-features-clustering > - > > Key: CXF-8849 > URL: https://issues.apache.org/jira/browse/CXF-8849 > 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-8874) Get rid of EasyMock in cxf-rt-rs-security-sso-oidc
[ https://issues.apache.org/jira/browse/CXF-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8874. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-rs-security-sso-oidc > -- > > Key: CXF-8874 > URL: https://issues.apache.org/jira/browse/CXF-8874 > 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-8869) Get rid of EasyMock in cxf-rt-rs-extension-search
[ https://issues.apache.org/jira/browse/CXF-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8869. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-rs-extension-search > - > > Key: CXF-8869 > URL: https://issues.apache.org/jira/browse/CXF-8869 > 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-8873) Get rid of EasyMock in cxf-rt-rs-security-oauth2-saml
[ https://issues.apache.org/jira/browse/CXF-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8873. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-rs-security-oauth2-saml > - > > Key: CXF-8873 > URL: https://issues.apache.org/jira/browse/CXF-8873 > 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] [Commented] (CXF-8914) No content-length header after upgrade CXF from 3.5.6 to 3.6.1
[ https://issues.apache.org/jira/browse/CXF-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17759277#comment-17759277 ] Andriy Redko commented on CXF-8914: --- Hi [~stephan.naecker] , thank you a lot for the information. The workaround is inspired by this comment https://issues.apache.org/jira/browse/CXF-8885?focusedCommentId=17747647=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-17747647 . You basically need to define your own URLConnectionHTTPConduitFactory and add the bean to the Spring context, that should make it. We will try to provide a better options in the upcoming release. Thank you. > No content-length header after upgrade CXF from 3.5.6 to 3.6.1 > -- > > Key: CXF-8914 > URL: https://issues.apache.org/jira/browse/CXF-8914 > Project: CXF > Issue Type: Bug >Affects Versions: 3.6.1 > Environment: SpringBoot 2.7.13 >Reporter: Stephan Näcker >Priority: Major > > After updating the CXF dependency in our application from 3.5.6 to 3.6.1 it > does not add a content-length header anymore, when doing a multipart request > for a file upload. > I didn't find any information, how to let CXF set the header. Is it just > dependent of chunking? > Actually the application sets "allow chunking" to false. But I'm not sure, > how I can test, if this really works. > Thanks in advance for your help. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CXF-8855) Get rid of EasyMock in cxf-rt-ws-transfer
[ https://issues.apache.org/jira/browse/CXF-8855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8855. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-ws-transfer > - > > Key: CXF-8855 > URL: https://issues.apache.org/jira/browse/CXF-8855 > 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] [Comment Edited] (CXF-8914) No content-length header after upgrade CXF from 3.5.6 to 3.6.1
[
https://issues.apache.org/jira/browse/CXF-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757750#comment-17757750
]
Andriy Redko edited comment on CXF-8914 at 8/23/23 1:28 AM:
Hi [~stephan.naecker], I think this commit
[https://github.com/apache/cxf/commit/395cba5b5a6b6725e6a54d41ee9b3b1675ffbb43]
is the culprit, the {color:#2a00ff}"Content-Length"{color} header is filtered
out. By default in 3.6.1, CXF uses HttpClient as underlying client transport
and it does not (apparently) allow setting this header. One of the possible
options - switch to back to URLConnectionHTTPConduit, that should fix the
issue.
I would be happy to help you there but need a bit of help to understand how you
configure and run your application. Spring? Servlet Container? Something else?
was (Author: reta):
Hi [~stephan.naecker], I think this commit
[https://github.com/apache/cxf/commit/395cba5b5a6b6725e6a54d41ee9b3b1675ffbb43]
is the culprit, the {color:#2a00ff}"Content-Length"{color} header is filtered
out. By default in 3.6.1, CXF uses HttpClient as underlying client transport
and it does not (apparently) allow
setting this header. One of the possible options - switch to back to
URLConnectionHTTPConduit, that should fix the issue.
> No content-length header after upgrade CXF from 3.5.6 to 3.6.1
> --
>
> Key: CXF-8914
> URL: https://issues.apache.org/jira/browse/CXF-8914
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.6.1
> Environment: SpringBoot 2.7.13
>Reporter: Stephan Näcker
>Priority: Major
>
> After updating the CXF dependency in our application from 3.5.6 to 3.6.1 it
> does not add a content-length header anymore, when doing a multipart request
> for a file upload.
> I didn't find any information, how to let CXF set the header. Is it just
> dependent of chunking?
> Actually the application sets "allow chunking" to false. But I'm not sure,
> how I can test, if this really works.
> Thanks in advance for your help.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CXF-8914) No content-length header after upgrade CXF from 3.5.6 to 3.6.1
[
https://issues.apache.org/jira/browse/CXF-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17757750#comment-17757750
]
Andriy Redko commented on CXF-8914:
---
Hi [~stephan.naecker], I think this commit
[https://github.com/apache/cxf/commit/395cba5b5a6b6725e6a54d41ee9b3b1675ffbb43]
is the culprit, the {color:#2a00ff}"Content-Length"{color} header is filtered
out. By default in 3.6.1, CXF uses HttpClient as underlying client transport
and it does not (apparently) allow
setting this header. One of the possible options - switch to back to
URLConnectionHTTPConduit, that should fix the issue.
> No content-length header after upgrade CXF from 3.5.6 to 3.6.1
> --
>
> Key: CXF-8914
> URL: https://issues.apache.org/jira/browse/CXF-8914
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.6.1
> Environment: SpringBoot 2.7.13
>Reporter: Stephan Näcker
>Priority: Major
>
> After updating the CXF dependency in our application from 3.5.6 to 3.6.1 it
> does not add a content-length header anymore, when doing a multipart request
> for a file upload.
> I didn't find any information, how to let CXF set the header. Is it just
> dependent of chunking?
> Actually the application sets "allow chunking" to false. But I'm not sure,
> how I can test, if this really works.
> Thanks in advance for your help.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (CXF-8457) Provide OpenTelemetry support
[ https://issues.apache.org/jira/browse/CXF-8457?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8457: -- Description: The OpenTelemetry [1] is getting matured [2] and adopted widely. Although shims exists, it would be good to support it natively along with Zipkin and OpenTracing (which is deprecated [3]). [1] [https://github.com/open-telemetry/opentelemetry-java] [2] [https://github.com/open-telemetry/opentelemetry-java/releases/tag/v1.2.0] [3] [https://medium.com/opentracing/opentracing-has-been-archived-fb2848cfef67] Documentation: * [https://cwiki.apache.org/confluence/display/CXF20DOC/Using+OpenTelemetry] was: The OpenTelemetry [1] is getting matured [2] and adopted widely. Although shims exists, it would be good to support it natively along with Zipkin and OpenTracing (which is deprecated [3]). [1] [https://github.com/open-telemetry/opentelemetry-java] [2] [https://github.com/open-telemetry/opentelemetry-java/releases/tag/v1.2.0] [3] https://medium.com/opentracing/opentracing-has-been-archived-fb2848cfef67 > Provide OpenTelemetry support > - > > Key: CXF-8457 > URL: https://issues.apache.org/jira/browse/CXF-8457 > Project: CXF > Issue Type: Improvement > Components: Tracing >Reporter: Andriy Redko >Priority: Major > Fix For: 3.5.7, 3.6.2, 4.0.3 > > > The OpenTelemetry [1] is getting matured [2] and adopted widely. Although > shims exists, it would be good to support it natively along with Zipkin and > OpenTracing (which is deprecated [3]). > [1] [https://github.com/open-telemetry/opentelemetry-java] > [2] [https://github.com/open-telemetry/opentelemetry-java/releases/tag/v1.2.0] > [3] > [https://medium.com/opentracing/opentracing-has-been-archived-fb2848cfef67] > > Documentation: > * [https://cwiki.apache.org/confluence/display/CXF20DOC/Using+OpenTelemetry] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8817) Add support for Micrometer Observation
[ https://issues.apache.org/jira/browse/CXF-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8817: -- Description: I'm a co-maintainer of Spring Cloud Sleuth and Micrometer projects (together with Tommy Ludwig and Jonatan Ivanov). [Micrometer Observation|https://micrometer.io/docs/observation] is coming as part of the Micrometer 1.10 release and [Micrometer Tracing|https://micrometer.io/docs/tracing] is a new project. The idea of Micrometer Observation is that you instrument code once but you get multiple benefits out of it - e.g. you can get tracing, metrics, logging or whatever you see fit). Since this project already supports Micrometer I was curious if there's interest in adding Micrometer Observation support so that automatically (when on classpath) except for metrics, spans could be created and tracing context propagation could happen too. In other words metrics and tracing of this project could be created + if there are Micrometer Observation compatible projects, then they will join the whole graph (e.g. whole Spring Framework 6 is, Apache Dubbo, Resilience4j etc.). If there's interest in adding that feature, I can provide a PR. Documentation: * [https://cwiki.apache.org/confluence/display/CXF20DOC/Using+Micrometer+Observation] was: I'm a co-maintainer of Spring Cloud Sleuth and Micrometer projects (together with Tommy Ludwig and Jonatan Ivanov). [Micrometer Observation|https://micrometer.io/docs/observation] is coming as part of the Micrometer 1.10 release and [Micrometer Tracing|https://micrometer.io/docs/tracing] is a new project. The idea of Micrometer Observation is that you instrument code once but you get multiple benefits out of it - e.g. you can get tracing, metrics, logging or whatever you see fit). Since this project already supports Micrometer I was curious if there's interest in adding Micrometer Observation support so that automatically (when on classpath) except for metrics, spans could be created and tracing context propagation could happen too. In other words metrics and tracing of this project could be created + if there are Micrometer Observation compatible projects, then they will join the whole graph (e.g. whole Spring Framework 6 is, Apache Dubbo, Resilience4j etc.). If there's interest in adding that feature, I can provide a PR. > Add support for Micrometer Observation > -- > > Key: CXF-8817 > URL: https://issues.apache.org/jira/browse/CXF-8817 > Project: CXF > Issue Type: New Feature > Components: Core >Reporter: Marcin Grzejszczak >Priority: Major > Fix For: 4.0.3 > > > I'm a co-maintainer of Spring Cloud Sleuth and Micrometer projects (together > with Tommy Ludwig and Jonatan Ivanov). > [Micrometer Observation|https://micrometer.io/docs/observation] is coming as > part of the Micrometer 1.10 release and [Micrometer > Tracing|https://micrometer.io/docs/tracing] is a new project. The idea of > Micrometer Observation is that you instrument code once but you get multiple > benefits out of it - e.g. you can get tracing, metrics, logging or whatever > you see fit). > Since this project already supports Micrometer I was curious if there's > interest in adding Micrometer Observation support so that automatically (when > on classpath) except for metrics, spans could be created and tracing context > propagation could happen too. In other words metrics and tracing of this > project could be created + if there are Micrometer Observation compatible > projects, then they will join the whole graph (e.g. whole Spring Framework 6 > is, Apache Dubbo, Resilience4j etc.). > If there's interest in adding that feature, I can provide a PR. > Documentation: > * > [https://cwiki.apache.org/confluence/display/CXF20DOC/Using+Micrometer+Observation] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CXF-8864) Get rid of EasyMock in cxf-rt-transports-jms
[ https://issues.apache.org/jira/browse/CXF-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8864. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-transports-jms > > > Key: CXF-8864 > URL: https://issues.apache.org/jira/browse/CXF-8864 > 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] [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
[X] ./integration/jca/pom.xml
[X] ./rt/bindings/coloc/pom.xml
[X] ./rt/bindings/corba/pom.xml
[X] ./rt/bindings/soap/pom.xml
[X] ./rt/databinding/aegis/pom.xml
[X] ./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
[X] ./rt/rs/microprofile-client/pom.xml
[X] ./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
[X] ./rt/transports/http-netty/netty-client/pom.xml
[X] ./rt/transports/http-netty/netty-server/pom.xml
[X] ./rt/transports/http-undertow/pom.xml
[X] ./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
[X] ./integration/jca/pom.xml
[X] ./rt/bindings/coloc/pom.xml
[X] ./rt/bindings/corba/pom.xml
[X] ./rt/bindings/soap/pom.xml
[X] ./rt/databinding/aegis/pom.xml
[X] ./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
[X] ./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
[X] ./rt/transports/http-netty/netty-client/pom.xml
[X] ./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]
[jira] [Updated] (CXF-8874) Get rid of EasyMock in cxf-rt-rs-security-sso-oidc
[ https://issues.apache.org/jira/browse/CXF-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8874: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in cxf-rt-rs-security-sso-oidc > -- > > Key: CXF-8874 > URL: https://issues.apache.org/jira/browse/CXF-8874 > Project: CXF > Issue Type: Sub-task >Reporter: 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-8874) Get rid of EasyMock in cxf-rt-rs-security-sso-oidc
[ https://issues.apache.org/jira/browse/CXF-8874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8874: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-rs-security-sso-oidc > -- > > Key: CXF-8874 > URL: https://issues.apache.org/jira/browse/CXF-8874 > 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] [Updated] (CXF-8873) Get rid of EasyMock in cxf-rt-rs-security-oauth2-saml
[ https://issues.apache.org/jira/browse/CXF-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8873: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in cxf-rt-rs-security-oauth2-saml > - > > Key: CXF-8873 > URL: https://issues.apache.org/jira/browse/CXF-8873 > 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] [Updated] (CXF-8869) Get rid of EasyMock in cxf-rt-rs-extension-search
[ https://issues.apache.org/jira/browse/CXF-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8869: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in cxf-rt-rs-extension-search > - > > Key: CXF-8869 > URL: https://issues.apache.org/jira/browse/CXF-8869 > 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-8873) Get rid of EasyMock in cxf-rt-rs-security-oauth2-saml
[ https://issues.apache.org/jira/browse/CXF-8873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8873: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-rs-security-oauth2-saml > - > > Key: CXF-8873 > URL: https://issues.apache.org/jira/browse/CXF-8873 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CXF-8868) Get rid of EasyMock in cxf-rt-rs-extension-providers
[ https://issues.apache.org/jira/browse/CXF-8868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8868: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-rs-extension-providers > > > Key: CXF-8868 > URL: https://issues.apache.org/jira/browse/CXF-8868 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8867) Get rid of EasyMock in cxf-rt-rs-client
[ https://issues.apache.org/jira/browse/CXF-8867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8867: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in cxf-rt-rs-client > --- > > Key: CXF-8867 > URL: https://issues.apache.org/jira/browse/CXF-8867 > 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-8869) Get rid of EasyMock in cxf-rt-rs-extension-search
[ https://issues.apache.org/jira/browse/CXF-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8869: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-rs-extension-search > - > > Key: CXF-8869 > URL: https://issues.apache.org/jira/browse/CXF-8869 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8868) Get rid of EasyMock in cxf-rt-rs-extension-providers
[ https://issues.apache.org/jira/browse/CXF-8868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8868: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in cxf-rt-rs-extension-providers > > > Key: CXF-8868 > URL: https://issues.apache.org/jira/browse/CXF-8868 > 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-8867) Get rid of EasyMock in cxf-rt-rs-client
[ https://issues.apache.org/jira/browse/CXF-8867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8867: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-rs-client > --- > > Key: CXF-8867 > URL: https://issues.apache.org/jira/browse/CXF-8867 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CXF-8848) Get rid of EasyMock in cxf-rt-databinding-jaxb
[ https://issues.apache.org/jira/browse/CXF-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8848. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-databinding-jaxb > -- > > Key: CXF-8848 > URL: https://issues.apache.org/jira/browse/CXF-8848 > 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-8917) Get rid of EasyMock in cxf-rt-transports-http-hc
[ https://issues.apache.org/jira/browse/CXF-8917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8917. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-transports-http-hc > > > Key: CXF-8917 > URL: https://issues.apache.org/jira/browse/CXF-8917 > Project: CXF > Issue Type: Sub-task >Affects Versions: 3.6.1 >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 3.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (CXF-8917) Get rid of EasyMock in cxf-rt-transports-http-hc
Andriy Redko created CXF-8917: - Summary: Get rid of EasyMock in cxf-rt-transports-http-hc Key: CXF-8917 URL: https://issues.apache.org/jira/browse/CXF-8917 Project: CXF Issue Type: Sub-task Affects Versions: 3.6.1 Reporter: Andriy Redko Assignee: Andriy Redko Fix For: 3.6.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8911) Allow creating a custom CXFHttpAsyncResponseConsumer
[
https://issues.apache.org/jira/browse/CXF-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755938#comment-17755938
]
Andriy Redko commented on CXF-8911:
---
[~dufoli] [~ppalaga] another one which seems to be less intrusive is:
{noformat}
public interface AsyncResponseListenerFactory {
AsyncResponseListener create();
}
public interface AsyncResponseListener {
void onBeforeReceived(HttpResponse response);
void onAfterReceived(HttpResponse response);
} {noformat}
The CXFResponseCallback would do something like that:
{noformat}
CXFResponseCallback responseCallback = new CXFResponseCallback() {
@Override
public void responseReceived(HttpResponse response) {
listener.onBeforeReceived(response);
setHttpResponse(response);
listener.onAfterReceived(response);
}
}; {noformat}
Would this one work for you folks? The AsyncResponseListener would be created
in the same thread as the CXFResponseCallback , every time.
> Allow creating a custom CXFHttpAsyncResponseConsumer
>
>
> Key: CXF-8911
> URL: https://issues.apache.org/jira/browse/CXF-8911
> Project: CXF
> Issue Type: New Feature
>Reporter: Peter Palaga
>Priority: Major
>
> We recently got a [bug
> report|https://github.com/quarkiverse/quarkus-cxf/issues/947] in Quarkus CXF
> complaining about non-working context propagation with CXF HC5 client.
> The problem was that if the client is called in context of a Quarkus REST
> endpoint, whose vert.x thread has the request context setup properly, the
> request scoped beans are then not accessible e.g. from
> ContainerRequestFilters which run in in a different thread.
> To make it work, we would need wrap the creation of
> CXFHttpAsyncResponseConsumer in some code storing the context of the creation
> thread into a wrapping method that can then be executed by some other thread.
> I was able to do this by overriding some default classes. What I did can be
> seen around here:
> https://github.com/quarkiverse/quarkus-cxf/pull/950/files#diff-568a3d75d004f9f41c6130854755ebb2beae2f30308cc45aa98492d09bac2ecc
> This solution is by no means elegant and I wonder whether it would be
> feasible to implement some new API to allow creating custom
> CXFHttpAsyncResponseConsumers?
> Maybe we could introduce some kind of CXFHttpAsyncResponseConsumerFactory?
> I am quite new to CXF internals, so I'd be thankful for any hints how to
> proceed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CXF-8913) Avoid 3rd party maven repository for OpenSAML
[ https://issues.apache.org/jira/browse/CXF-8913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755933#comment-17755933 ] Andriy Redko commented on CXF-8913: --- Thanks a lot [~coheigea] ! > Avoid 3rd party maven repository for OpenSAML > - > > Key: CXF-8913 > URL: https://issues.apache.org/jira/browse/CXF-8913 > Project: CXF > Issue Type: Improvement > Components: WS-* Components >Affects Versions: 4.0.2 >Reporter: Claus Ibsen >Priority: Major > > Apache CXF depends on OpenSAML from Apache WSSJ project > However this commit causes wss4j to download JARs from NOT maven central but > from > https://build.shibboleth.net/nexus/content/groups/public > https://github.com/apache/ws-wss4j/commit/e4a33efcb2b474a1da2b2c08f815b2718e111823 > Is there a way for Apache CXF to only use JARs from maven central. There is a > trust issue when JARs are NOT downloaded from central. > At Apache Camel we only download from maven central - except for camel-jira > which sadly had to download from Atlassian. We are considering deprecating > and removing this component for that reason. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CXF-8843) Get rid of EasyMock in cxf-integration-jca
[ https://issues.apache.org/jira/browse/CXF-8843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8843. --- Resolution: Fixed > Get rid of EasyMock in cxf-integration-jca > -- > > Key: CXF-8843 > URL: https://issues.apache.org/jira/browse/CXF-8843 > 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] [Commented] (CXF-8911) Allow creating a custom CXFHttpAsyncResponseConsumer
[
https://issues.apache.org/jira/browse/CXF-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755751#comment-17755751
]
Andriy Redko commented on CXF-8911:
---
The solution I came up with so far is that (the AsyncResponseCallbackFactory
is set per AsyncHTTPConduitFactory):
{noformat}
public interface AsyncResponseCallbackFactory {
AsyncResponseCallback create();
}
public interface AsyncResponseCallback {
default void responseReceived(HttpResponse response, CXFResponseCallback
callback) {
callback.responseReceived(response);
}
}
{noformat}
> Allow creating a custom CXFHttpAsyncResponseConsumer
>
>
> Key: CXF-8911
> URL: https://issues.apache.org/jira/browse/CXF-8911
> Project: CXF
> Issue Type: New Feature
>Reporter: Peter Palaga
>Priority: Major
>
> We recently got a [bug
> report|https://github.com/quarkiverse/quarkus-cxf/issues/947] in Quarkus CXF
> complaining about non-working context propagation with CXF HC5 client.
> The problem was that if the client is called in context of a Quarkus REST
> endpoint, whose vert.x thread has the request context setup properly, the
> request scoped beans are then not accessible e.g. from
> ContainerRequestFilters which run in in a different thread.
> To make it work, we would need wrap the creation of
> CXFHttpAsyncResponseConsumer in some code storing the context of the creation
> thread into a wrapping method that can then be executed by some other thread.
> I was able to do this by overriding some default classes. What I did can be
> seen around here:
> https://github.com/quarkiverse/quarkus-cxf/pull/950/files#diff-568a3d75d004f9f41c6130854755ebb2beae2f30308cc45aa98492d09bac2ecc
> This solution is by no means elegant and I wonder whether it would be
> feasible to implement some new API to allow creating custom
> CXFHttpAsyncResponseConsumers?
> Maybe we could introduce some kind of CXFHttpAsyncResponseConsumerFactory?
> I am quite new to CXF internals, so I'd be thankful for any hints how to
> proceed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CXF-8913) Avoid 3rd party maven repository for OpenSAML
[ https://issues.apache.org/jira/browse/CXF-8913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755729#comment-17755729 ] Andriy Redko edited comment on CXF-8913 at 8/17/23 11:20 PM: - AFAIK, as you also posted, opensaml is transitive dependency of wss4j-ws-security-common (but also used by cxf-rt-ws-security), [~coheigea] could you advice please if opensaml could be made optional? Or if split make sense (as we have for cxf-rt-security)? was (Author: reta): AFAIK, as you also posted, opensaml is transitive dependency of wss4j-ws-security-common, [~coheigea] could you advice please if opensaml could be made optional? Or if split make sense (as we have for cxf-rt-security)? > Avoid 3rd party maven repository for OpenSAML > - > > Key: CXF-8913 > URL: https://issues.apache.org/jira/browse/CXF-8913 > Project: CXF > Issue Type: Improvement > Components: WS-* Components >Affects Versions: 4.0.2 >Reporter: Claus Ibsen >Priority: Major > > Apache CXF depends on OpenSAML from Apache WSSJ project > However this commit causes wss4j to download JARs from NOT maven central but > from > https://build.shibboleth.net/nexus/content/groups/public > https://github.com/apache/ws-wss4j/commit/e4a33efcb2b474a1da2b2c08f815b2718e111823 > Is there a way for Apache CXF to only use JARs from maven central. There is a > trust issue when JARs are NOT downloaded from central. > At Apache Camel we only download from maven central - except for camel-jira > which sadly had to download from Atlassian. We are considering deprecating > and removing this component for that reason. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8913) Avoid 3rd party maven repository for OpenSAML
[ https://issues.apache.org/jira/browse/CXF-8913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755729#comment-17755729 ] Andriy Redko commented on CXF-8913: --- AFAIK, as you also posted, opensaml is transitive dependency of wss4j-ws-security-common, [~coheigea] could you advice please if opensaml could be made optional? Or if split make sense (as we have for cxf-rt-security)? > Avoid 3rd party maven repository for OpenSAML > - > > Key: CXF-8913 > URL: https://issues.apache.org/jira/browse/CXF-8913 > Project: CXF > Issue Type: Improvement > Components: WS-* Components >Affects Versions: 4.0.2 >Reporter: Claus Ibsen >Priority: Major > > Apache CXF depends on OpenSAML from Apache WSSJ project > However this commit causes wss4j to download JARs from NOT maven central but > from > https://build.shibboleth.net/nexus/content/groups/public > https://github.com/apache/ws-wss4j/commit/e4a33efcb2b474a1da2b2c08f815b2718e111823 > Is there a way for Apache CXF to only use JARs from maven central. There is a > trust issue when JARs are NOT downloaded from central. > At Apache Camel we only download from maven central - except for camel-jira > which sadly had to download from Atlassian. We are considering deprecating > and removing this component for that reason. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8914) No content-length header after upgrade CXF from 3.5.6 to 3.6.1
[ https://issues.apache.org/jira/browse/CXF-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755728#comment-17755728 ] Andriy Redko commented on CXF-8914: --- Thanks [~stephan.naecker] , I do see that Content-Length is indeed not present anymore > No content-length header after upgrade CXF from 3.5.6 to 3.6.1 > -- > > Key: CXF-8914 > URL: https://issues.apache.org/jira/browse/CXF-8914 > Project: CXF > Issue Type: Bug >Affects Versions: 3.6.1 > Environment: SpringBoot 2.7.13 >Reporter: Stephan Näcker >Priority: Major > > After updating the CXF dependency in our application from 3.5.6 to 3.6.1 it > does not add a content-length header anymore, when doing a multipart request > for a file upload. > I didn't find any information, how to let CXF set the header. Is it just > dependent of chunking? > Actually the application sets "allow chunking" to false. But I'm not sure, > how I can test, if this really works. > Thanks in advance for your help. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (CXF-8911) Allow creating a custom CXFHttpAsyncResponseConsumer
[
https://issues.apache.org/jira/browse/CXF-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755724#comment-17755724
]
Andriy Redko edited comment on CXF-8911 at 8/17/23 10:39 PM:
-
Hey [~dufoli] ,
I haven't had time to get back to the issue, apologies, but there was only one
problem I stumbled upon related to CXFResponseCallback, the default one
(current) calls the {color:#00}setHttpResponse(..) method of the outer
{color}{color:#00}AsyncWrappedOutputStream{color} instance:
{noformat}
CXFResponseCallback responseCallback = new CXFResponseCallback() {
@Override
public void responseReceived(HttpResponse response) {
setHttpResponse(response);
}
};{noformat}
It has to be done and if we replace the CXFResponseCallback with factory, there
is no way to enforce the default behavior (and we if don't the client will hang
forever).
was (Author: reta):
Hey [~dufoli] ,
I haven't had time to get back to the issue, apologies, but there was only one
problem I stumbled upon related to CXFResponseCallback, the default one
(current) calls the {color:#00}setHttpResponse(..) method of the outer
{color}{color:#00}AsyncWrappedOutputStream{color} instance:
{noformat}
CXFResponseCallback responseCallback = new CXFResponseCallback() {
@Override
public void responseReceived(HttpResponse response) {
setHttpResponse(response);
}
};{noformat}
It has to be done and if we replace the CXFResponseCallback with factory, there
is no way to enforce the default behavior (and we don't the client will hang
forever).
> Allow creating a custom CXFHttpAsyncResponseConsumer
>
>
> Key: CXF-8911
> URL: https://issues.apache.org/jira/browse/CXF-8911
> Project: CXF
> Issue Type: New Feature
>Reporter: Peter Palaga
>Priority: Major
>
> We recently got a [bug
> report|https://github.com/quarkiverse/quarkus-cxf/issues/947] in Quarkus CXF
> complaining about non-working context propagation with CXF HC5 client.
> The problem was that if the client is called in context of a Quarkus REST
> endpoint, whose vert.x thread has the request context setup properly, the
> request scoped beans are then not accessible e.g. from
> ContainerRequestFilters which run in in a different thread.
> To make it work, we would need wrap the creation of
> CXFHttpAsyncResponseConsumer in some code storing the context of the creation
> thread into a wrapping method that can then be executed by some other thread.
> I was able to do this by overriding some default classes. What I did can be
> seen around here:
> https://github.com/quarkiverse/quarkus-cxf/pull/950/files#diff-568a3d75d004f9f41c6130854755ebb2beae2f30308cc45aa98492d09bac2ecc
> This solution is by no means elegant and I wonder whether it would be
> feasible to implement some new API to allow creating custom
> CXFHttpAsyncResponseConsumers?
> Maybe we could introduce some kind of CXFHttpAsyncResponseConsumerFactory?
> I am quite new to CXF internals, so I'd be thankful for any hints how to
> proceed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CXF-8911) Allow creating a custom CXFHttpAsyncResponseConsumer
[
https://issues.apache.org/jira/browse/CXF-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755724#comment-17755724
]
Andriy Redko edited comment on CXF-8911 at 8/17/23 10:38 PM:
-
Hey [~dufoli] ,
I haven't had time to get back to the issue, apologies, but there was only one
problem I stumbled upon related to CXFResponseCallback, the default one
(current) calls the {color:#00}setHttpResponse(..) method of the outer
{color}{color:#00}AsyncWrappedOutputStream{color} instance:
{noformat}
CXFResponseCallback responseCallback = new CXFResponseCallback() {
@Override
public void responseReceived(HttpResponse response) {
setHttpResponse(response);
}
};{noformat}
It has to be done and if we replace the CXFResponseCallback with factory, there
is no way to enforce the default behavior (and we don't the client will hang
forever).
was (Author: reta):
Hey [~dufoli] ,
I haven't had time to get back to the issue, apologies, but there was only one
problem I stumbled upon related to CXFResponseCallback, the default one
(current) calls the {color:#00}setHttpResponse(..) method of the outer
{color}{color:#00}AsyncWrappedOutputStream{color} instance:
{noformat}
CXFResponseCallback responseCallback = new CXFResponseCallback() {
@Override
public void responseReceived(HttpResponse response) {
setHttpResponse(response);
}
};{noformat}
It has to be done and there if we replace the CXFResponseCallback with factory,
there is no way to enforce the default behavior (and we don't the client will
hang forever).
> Allow creating a custom CXFHttpAsyncResponseConsumer
>
>
> Key: CXF-8911
> URL: https://issues.apache.org/jira/browse/CXF-8911
> Project: CXF
> Issue Type: New Feature
>Reporter: Peter Palaga
>Priority: Major
>
> We recently got a [bug
> report|https://github.com/quarkiverse/quarkus-cxf/issues/947] in Quarkus CXF
> complaining about non-working context propagation with CXF HC5 client.
> The problem was that if the client is called in context of a Quarkus REST
> endpoint, whose vert.x thread has the request context setup properly, the
> request scoped beans are then not accessible e.g. from
> ContainerRequestFilters which run in in a different thread.
> To make it work, we would need wrap the creation of
> CXFHttpAsyncResponseConsumer in some code storing the context of the creation
> thread into a wrapping method that can then be executed by some other thread.
> I was able to do this by overriding some default classes. What I did can be
> seen around here:
> https://github.com/quarkiverse/quarkus-cxf/pull/950/files#diff-568a3d75d004f9f41c6130854755ebb2beae2f30308cc45aa98492d09bac2ecc
> This solution is by no means elegant and I wonder whether it would be
> feasible to implement some new API to allow creating custom
> CXFHttpAsyncResponseConsumers?
> Maybe we could introduce some kind of CXFHttpAsyncResponseConsumerFactory?
> I am quite new to CXF internals, so I'd be thankful for any hints how to
> proceed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (CXF-8911) Allow creating a custom CXFHttpAsyncResponseConsumer
[
https://issues.apache.org/jira/browse/CXF-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755724#comment-17755724
]
Andriy Redko edited comment on CXF-8911 at 8/17/23 10:38 PM:
-
Hey [~dufoli] ,
I haven't had time to get back to the issue, apologies, but there was only one
problem I stumbled upon related to CXFResponseCallback, the default one
(current) calls the {color:#00}setHttpResponse(..) method of the outer
{color}{color:#00}AsyncWrappedOutputStream{color} instance:
{noformat}
CXFResponseCallback responseCallback = new CXFResponseCallback() {
@Override
public void responseReceived(HttpResponse response) {
setHttpResponse(response);
}
};{noformat}
It has to be done and there if we replace the CXFResponseCallback with factory,
there is no way to enforce the default behavior (and we don't the client will
hang forever).
was (Author: reta):
Hey [~dufoli] ,
I haven't had time to get back to the issue, apologies, but there was only one
problem stumbled upon related to CXFResponseCallback, the default one
(current) calls the {color:#00}setHttpResponse(..) method of the outer
{color}{color:#00}AsyncWrappedOutputStream{color} instance:
{noformat}
CXFResponseCallback responseCallback = new CXFResponseCallback() {
@Override
public void responseReceived(HttpResponse response) {
setHttpResponse(response);
}
};{noformat}
It has to be done and there if we replace the CXFResponseCallback with factory,
there is no way to enforce the default behavior (and we don't the client will
hang forever).
> Allow creating a custom CXFHttpAsyncResponseConsumer
>
>
> Key: CXF-8911
> URL: https://issues.apache.org/jira/browse/CXF-8911
> Project: CXF
> Issue Type: New Feature
>Reporter: Peter Palaga
>Priority: Major
>
> We recently got a [bug
> report|https://github.com/quarkiverse/quarkus-cxf/issues/947] in Quarkus CXF
> complaining about non-working context propagation with CXF HC5 client.
> The problem was that if the client is called in context of a Quarkus REST
> endpoint, whose vert.x thread has the request context setup properly, the
> request scoped beans are then not accessible e.g. from
> ContainerRequestFilters which run in in a different thread.
> To make it work, we would need wrap the creation of
> CXFHttpAsyncResponseConsumer in some code storing the context of the creation
> thread into a wrapping method that can then be executed by some other thread.
> I was able to do this by overriding some default classes. What I did can be
> seen around here:
> https://github.com/quarkiverse/quarkus-cxf/pull/950/files#diff-568a3d75d004f9f41c6130854755ebb2beae2f30308cc45aa98492d09bac2ecc
> This solution is by no means elegant and I wonder whether it would be
> feasible to implement some new API to allow creating custom
> CXFHttpAsyncResponseConsumers?
> Maybe we could introduce some kind of CXFHttpAsyncResponseConsumerFactory?
> I am quite new to CXF internals, so I'd be thankful for any hints how to
> proceed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (CXF-8911) Allow creating a custom CXFHttpAsyncResponseConsumer
[
https://issues.apache.org/jira/browse/CXF-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755724#comment-17755724
]
Andriy Redko commented on CXF-8911:
---
Hey [~dufoli] ,
I haven't had time to get back to the issue, apologies, but there was only one
problem stumbled upon related to CXFResponseCallback, the default one
(current) calls the {color:#00}setHttpResponse(..) method of the outer
{color}{color:#00}AsyncWrappedOutputStream{color} instance:
{noformat}
CXFResponseCallback responseCallback = new CXFResponseCallback() {
@Override
public void responseReceived(HttpResponse response) {
setHttpResponse(response);
}
};{noformat}
It has to be done and there if we replace the CXFResponseCallback with factory,
there is no way to enforce the default behavior (and we don't the client will
hang forever).
> Allow creating a custom CXFHttpAsyncResponseConsumer
>
>
> Key: CXF-8911
> URL: https://issues.apache.org/jira/browse/CXF-8911
> Project: CXF
> Issue Type: New Feature
>Reporter: Peter Palaga
>Priority: Major
>
> We recently got a [bug
> report|https://github.com/quarkiverse/quarkus-cxf/issues/947] in Quarkus CXF
> complaining about non-working context propagation with CXF HC5 client.
> The problem was that if the client is called in context of a Quarkus REST
> endpoint, whose vert.x thread has the request context setup properly, the
> request scoped beans are then not accessible e.g. from
> ContainerRequestFilters which run in in a different thread.
> To make it work, we would need wrap the creation of
> CXFHttpAsyncResponseConsumer in some code storing the context of the creation
> thread into a wrapping method that can then be executed by some other thread.
> I was able to do this by overriding some default classes. What I did can be
> seen around here:
> https://github.com/quarkiverse/quarkus-cxf/pull/950/files#diff-568a3d75d004f9f41c6130854755ebb2beae2f30308cc45aa98492d09bac2ecc
> This solution is by no means elegant and I wonder whether it would be
> feasible to implement some new API to allow creating custom
> CXFHttpAsyncResponseConsumers?
> Maybe we could introduce some kind of CXFHttpAsyncResponseConsumerFactory?
> I am quite new to CXF internals, so I'd be thankful for any hints how to
> proceed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Resolved] (CXF-8872) Get rid of EasyMock in cxf-rt-rs-security-oauth2
[ https://issues.apache.org/jira/browse/CXF-8872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8872. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-rs-security-oauth2 > > > Key: CXF-8872 > URL: https://issues.apache.org/jira/browse/CXF-8872 > 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] [Commented] (CXF-8914) No content-length header after upgrade CXF from 3.5.6 to 3.6.1
[ https://issues.apache.org/jira/browse/CXF-8914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17755304#comment-17755304 ] Andriy Redko commented on CXF-8914: --- Thanks for reporting the issue [~stephan.naecker] , could you please, if possible, share the headers being sent in 3.5.6 and 3.6.1? thank you > No content-length header after upgrade CXF from 3.5.6 to 3.6.1 > -- > > Key: CXF-8914 > URL: https://issues.apache.org/jira/browse/CXF-8914 > Project: CXF > Issue Type: Bug >Affects Versions: 3.6.1 > Environment: SpringBoot 2.7.13 >Reporter: Stephan Näcker >Priority: Major > > After updating the CXF dependency in our application from 3.5.6 to 3.6.1 it > does not add a content-length header anymore, when doing a multipart request > for a file upload. > I didn't find any information, how to let CXF set the header. Is it just > dependent of chunking? > Actually the application sets "allow chunking" to false. But I'm not sure, > how I can test, if this really works. > Thanks in advance for your help. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8671) Support Jakarta EE 10
[ https://issues.apache.org/jira/browse/CXF-8671?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8671: -- Description: Support Jakarta EE 10 Jakarta EE 10 has Landed - [https://jakartaee-ambassadors.io/2022/09/22/jakarta-ee-10-released/] [https://jakarta.ee/release/10/] [https://www.infoq.com/news/2023/01/glassfish-delivers-support-jdk17/] Specs: * Jakarta Activation 2.1* * Jakarta Authentication 3.0* * Jakarta Authorization 2.1* * Jakarta Batch 2.1* * Jakarta Bean Validation 3.0 * Jakarta Common Annotations 2.1* * Jakarta Concurrency 3.0* * Jakarta Connectors 2.1* * Jakarta Contexts and Dependency Injection 4.0* * Jakarta Debugging Support for Other Languages 2.0 * Jakarta Dependency Injection 2.0 * Jakarta Enterprise Beans 4.0 (except for Jakarta Enterprise Beans entity beans and associated Jakarta Enterprise Beans QL, and embedded container, which have been made removed) * Jakarta Expression Language 5.0* * Jakarta Interceptors 2.1* * Jakarta JSON Processing 2.1* * Jakarta JSON Binding 3.0* * Jakarta Mail 2.1* * Jakarta Managed Beans 2.0 * Jakarta Messaging 3.1* * Jakarta Persistence 3.1* * Jakarta RESTful Web Services 3.1* * Jakarta Security 3.0* * Jakarta Servlet 6.0* * Jakarta Server Faces 4.0* * Jakarta Server Pages 3.1* * Jakarta Standard Tag Library 3.0* * Jakarta Transactions 2.0 * Jakarta WebSocket 2.1* * Jakarta Enterprise Beans 3.2 and earlier entity beans and associated Jakarta Enterprise Beans QL * Jakarta Enterprise Beans 2.x API group * Jakarta Enterprise Web Services 2.0 * Jakarta SOAP with Attachments 3.0* * Jakarta XML Web Services 4.0* * Jakarta XML Binding 4.0* Rest Client TCK update: - [https://github.com/eclipse/microprofile-rest-client/pull/352] Updates required: - Undertow 2.3.x - Jetty 12 ([https://github.com/eclipse/jetty.project/releases/tag/jetty-12.0.0.beta0]) - Hibernate Validator 8 ([https://hibernate.org/validator/releases/8.0/)] - Hibernate 6.2 ([https://in.relation.to/2023/06/01/hibernate-orm-624-final/]) - Weld 5 ([https://weld.cdi-spec.org/news/2022/04/29/weld-500Final/]) - Hibernate 6.2.1 ([https://hibernate.org/orm/releases/6.2/], [https://in.relation.to/2023/03/30/orm-62-final/, https://in.relation.to/2023/04/14/hibernate-orm-621-final/|https://in.relation.to/2023/03/30/orm-62-final/]) - Spring Boot 3.1 ([https://github.com/spring-projects/spring-boot/releases/tag/v3.1.0]) - Spring Security 6.1 ([https://github.com/spring-projects/spring-security/releases/tag/6.1.0]) - Micrometer 1.11 ([https://github.com/micrometer-metrics/micrometer/releases/tag/v1.11.0|https://github.com/micrometer-metrics/micrometer/releases/tag/v1.11.0-M1]) - Micrometer Tracing 1.1 ([https://github.com/micrometer-metrics/tracing/releases/tag/v1.1.4)] - Spring LDAP 3.1 ([https://github.com/spring-projects/spring-ldap/releases/tag/3.1.0)] Microprofile 6.0 ([https://download.eclipse.org/microprofile/microprofile-6.0/microprofile-spec-6.0.html),] aligned with JakartaEE 10 core profile: - Microprofile OpenAPI 3.1 ([https://github.com/eclipse/microprofile-open-api/releases/tag/3.1]) - Angus Mail ([https://github.com/eclipse-ee4j/angus-mail/releases/tag/2.0.1]) - [https://github.com/arquillian/arquillian-container-weld/releases/tag/3.0.2.Final] was: Support Jakarta EE 10 Jakarta EE 10 has Landed - [https://jakartaee-ambassadors.io/2022/09/22/jakarta-ee-10-released/] [https://jakarta.ee/release/10/] [https://www.infoq.com/news/2023/01/glassfish-delivers-support-jdk17/] Specs: * Jakarta Activation 2.1* * Jakarta Authentication 3.0* * Jakarta Authorization 2.1* * Jakarta Batch 2.1* * Jakarta Bean Validation 3.0 * Jakarta Common Annotations 2.1* * Jakarta Concurrency 3.0* * Jakarta Connectors 2.1* * Jakarta Contexts and Dependency Injection 4.0* * Jakarta Debugging Support for Other Languages 2.0 * Jakarta Dependency Injection 2.0 * Jakarta Enterprise Beans 4.0 (except for Jakarta Enterprise Beans entity beans and associated Jakarta Enterprise Beans QL, and embedded container, which have been made removed) * Jakarta Expression Language 5.0* * Jakarta Interceptors 2.1* * Jakarta JSON Processing 2.1* * Jakarta JSON Binding 3.0* * Jakarta Mail 2.1* * Jakarta Managed Beans 2.0 * Jakarta Messaging 3.1* * Jakarta Persistence 3.1* * Jakarta RESTful Web Services 3.1* * Jakarta Security 3.0* * Jakarta Servlet 6.0* * Jakarta Server Faces 4.0* * Jakarta Server Pages 3.1* * Jakarta Standard Tag Library 3.0* * Jakarta Transactions 2.0 * Jakarta WebSocket 2.1* * Jakarta Enterprise Beans 3.2 and earlier entity beans and associated Jakarta Enterprise Beans QL * Jakarta Enterprise Beans 2.x API group * Jakarta Enterprise Web Services 2.0 * Jakarta SOAP with Attachments 3.0* * Jakarta XML Web Services 4.0* * Jakarta XML Binding 4.0*
[jira] [Commented] (CXF-8817) Add support for Micrometer Observation
[ https://issues.apache.org/jira/browse/CXF-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17754374#comment-17754374 ] Andriy Redko commented on CXF-8817: --- Micrometer Observations are only available since Micrometer 1.10.0 (see https://micrometer.io/docs/tracing#_purpose) > Add support for Micrometer Observation > -- > > Key: CXF-8817 > URL: https://issues.apache.org/jira/browse/CXF-8817 > Project: CXF > Issue Type: New Feature > Components: Core >Reporter: Marcin Grzejszczak >Priority: Major > Fix For: 4.0.3 > > > I'm a co-maintainer of Spring Cloud Sleuth and Micrometer projects (together > with Tommy Ludwig and Jonatan Ivanov). > [Micrometer Observation|https://micrometer.io/docs/observation] is coming as > part of the Micrometer 1.10 release and [Micrometer > Tracing|https://micrometer.io/docs/tracing] is a new project. The idea of > Micrometer Observation is that you instrument code once but you get multiple > benefits out of it - e.g. you can get tracing, metrics, logging or whatever > you see fit). > Since this project already supports Micrometer I was curious if there's > interest in adding Micrometer Observation support so that automatically (when > on classpath) except for metrics, spans could be created and tracing context > propagation could happen too. In other words metrics and tracing of this > project could be created + if there are Micrometer Observation compatible > projects, then they will join the whole graph (e.g. whole Spring Framework 6 > is, Apache Dubbo, Resilience4j etc.). > If there's interest in adding that feature, I can provide a PR. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8817) Add support for Micrometer Observation
[ https://issues.apache.org/jira/browse/CXF-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8817: -- Fix Version/s: (was: 3.5.7) (was: 3.6.2) > Add support for Micrometer Observation > -- > > Key: CXF-8817 > URL: https://issues.apache.org/jira/browse/CXF-8817 > Project: CXF > Issue Type: New Feature > Components: Core >Reporter: Marcin Grzejszczak >Priority: Major > Fix For: 4.0.3 > > > I'm a co-maintainer of Spring Cloud Sleuth and Micrometer projects (together > with Tommy Ludwig and Jonatan Ivanov). > [Micrometer Observation|https://micrometer.io/docs/observation] is coming as > part of the Micrometer 1.10 release and [Micrometer > Tracing|https://micrometer.io/docs/tracing] is a new project. The idea of > Micrometer Observation is that you instrument code once but you get multiple > benefits out of it - e.g. you can get tracing, metrics, logging or whatever > you see fit). > Since this project already supports Micrometer I was curious if there's > interest in adding Micrometer Observation support so that automatically (when > on classpath) except for metrics, spans could be created and tracing context > propagation could happen too. In other words metrics and tracing of this > project could be created + if there are Micrometer Observation compatible > projects, then they will join the whole graph (e.g. whole Spring Framework 6 > is, Apache Dubbo, Resilience4j etc.). > If there's interest in adding that feature, I can provide a PR. -- 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
[X] ./integration/jca/pom.xml
[X] ./rt/bindings/coloc/pom.xml
[X] ./rt/bindings/corba/pom.xml
[X] ./rt/bindings/soap/pom.xml
[X] ./rt/databinding/aegis/pom.xml
[X] ./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
[X] ./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
[X] ./rt/transports/http-netty/netty-client/pom.xml
[X] ./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
[X] ./integration/jca/pom.xml
[X] ./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
[X] ./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
[X] ./rt/transports/http-netty/netty-client/pom.xml
[X] ./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]
[jira] [Assigned] (CXF-8871) Get rid of EasyMock in cxf-rt-rs-mp-client
[ https://issues.apache.org/jira/browse/CXF-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8871: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-rs-mp-client > -- > > Key: CXF-8871 > URL: https://issues.apache.org/jira/browse/CXF-8871 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CXF-8864) Get rid of EasyMock in cxf-rt-transports-jms
[ https://issues.apache.org/jira/browse/CXF-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8864: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-transports-jms > > > Key: CXF-8864 > URL: https://issues.apache.org/jira/browse/CXF-8864 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8852) Get rid of EasyMock in cxf-services-xkms-x509-repo-ldap
[ https://issues.apache.org/jira/browse/CXF-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8852: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in cxf-services-xkms-x509-repo-ldap > --- > > Key: CXF-8852 > URL: https://issues.apache.org/jira/browse/CXF-8852 > 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] [Updated] (CXF-8864) Get rid of EasyMock in cxf-rt-transports-jms
[ https://issues.apache.org/jira/browse/CXF-8864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8864: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in cxf-rt-transports-jms > > > Key: CXF-8864 > URL: https://issues.apache.org/jira/browse/CXF-8864 > 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-8855) Get rid of EasyMock in cxf-rt-ws-transfer
[ https://issues.apache.org/jira/browse/CXF-8855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8855: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-ws-transfer > - > > Key: CXF-8855 > URL: https://issues.apache.org/jira/browse/CXF-8855 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8855) Get rid of EasyMock in cxf-rt-ws-transfer
[ https://issues.apache.org/jira/browse/CXF-8855?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8855: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in cxf-rt-ws-transfer > - > > Key: CXF-8855 > URL: https://issues.apache.org/jira/browse/CXF-8855 > 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] [Updated] (CXF-8871) Get rid of EasyMock in cxf-rt-rs-mp-client
[ https://issues.apache.org/jira/browse/CXF-8871?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8871: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in cxf-rt-rs-mp-client > -- > > Key: CXF-8871 > URL: https://issues.apache.org/jira/browse/CXF-8871 > 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] [Updated] (CXF-8851) Get rid of EasyMock in cxf-rt-features-throttling
[ https://issues.apache.org/jira/browse/CXF-8851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8851: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in cxf-rt-features-throttling > - > > Key: CXF-8851 > URL: https://issues.apache.org/jira/browse/CXF-8851 > 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-8852) Get rid of EasyMock in cxf-services-xkms-x509-repo-ldap
[ https://issues.apache.org/jira/browse/CXF-8852?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8852: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-services-xkms-x509-repo-ldap > --- > > Key: CXF-8852 > URL: https://issues.apache.org/jira/browse/CXF-8852 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CXF-8851) Get rid of EasyMock in cxf-rt-features-throttling
[ https://issues.apache.org/jira/browse/CXF-8851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8851: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-features-throttling > - > > Key: CXF-8851 > URL: https://issues.apache.org/jira/browse/CXF-8851 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CXF-8860) Get rid of EasyMock in cxf-rt-ws-rm
[ https://issues.apache.org/jira/browse/CXF-8860?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8860. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-ws-rm > --- > > Key: CXF-8860 > URL: https://issues.apache.org/jira/browse/CXF-8860 > 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-8853) Get rid of EasyMock in org.apache.cxf.services.xkms
[ https://issues.apache.org/jira/browse/CXF-8853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8853: - Assignee: Andriy Redko > Get rid of EasyMock in org.apache.cxf.services.xkms > --- > > Key: CXF-8853 > URL: https://issues.apache.org/jira/browse/CXF-8853 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8853) Get rid of EasyMock in org.apache.cxf.services.xkms
[ https://issues.apache.org/jira/browse/CXF-8853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8853: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in org.apache.cxf.services.xkms > --- > > Key: CXF-8853 > URL: https://issues.apache.org/jira/browse/CXF-8853 > 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] [Updated] (CXF-8850) Get rid of EasyMock in cxf-rt-features-logging
[ https://issues.apache.org/jira/browse/CXF-8850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8850: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in cxf-rt-features-logging > -- > > Key: CXF-8850 > URL: https://issues.apache.org/jira/browse/CXF-8850 > 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] [Updated] (CXF-8849) Get rid of EasyMock in cxf-rt-features-clustering
[ https://issues.apache.org/jira/browse/CXF-8849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8849: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in cxf-rt-features-clustering > - > > Key: CXF-8849 > URL: https://issues.apache.org/jira/browse/CXF-8849 > Project: CXF > Issue Type: Sub-task >Reporter: 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-8849) Get rid of EasyMock in cxf-rt-features-clustering
[ https://issues.apache.org/jira/browse/CXF-8849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8849: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-features-clustering > - > > Key: CXF-8849 > URL: https://issues.apache.org/jira/browse/CXF-8849 > 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-8850) Get rid of EasyMock in cxf-rt-features-logging
[ https://issues.apache.org/jira/browse/CXF-8850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8850: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-features-logging > -- > > Key: CXF-8850 > URL: https://issues.apache.org/jira/browse/CXF-8850 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CXF-8848) Get rid of EasyMock in cxf-rt-databinding-jaxb
[ https://issues.apache.org/jira/browse/CXF-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8848: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-databinding-jaxb > -- > > Key: CXF-8848 > URL: https://issues.apache.org/jira/browse/CXF-8848 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8848) Get rid of EasyMock in cxf-rt-databinding-jaxb
[ https://issues.apache.org/jira/browse/CXF-8848?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8848: -- Fix Version/s: 3.6.2 4.0.3 > Get rid of EasyMock in cxf-rt-databinding-jaxb > -- > > Key: CXF-8848 > URL: https://issues.apache.org/jira/browse/CXF-8848 > 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-8859) Get rid of EasyMock in cxf-rt-ws-security
[ https://issues.apache.org/jira/browse/CXF-8859?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8859. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-ws-security > - > > Key: CXF-8859 > URL: https://issues.apache.org/jira/browse/CXF-8859 > 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-8877) Get rid of EasyMock in cxf-rt-transports-http-netty-client
[ https://issues.apache.org/jira/browse/CXF-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8877. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-transports-http-netty-client > -- > > Key: CXF-8877 > URL: https://issues.apache.org/jira/browse/CXF-8877 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 3.5.7, 3.6.2, 4.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Deleted] (CXF-8875) Get rid of EasyMock in cxf-rt-transports-http-netty-client
[ https://issues.apache.org/jira/browse/CXF-8875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko deleted CXF-8875: -- > Get rid of EasyMock in cxf-rt-transports-http-netty-client > -- > > Key: CXF-8875 > URL: https://issues.apache.org/jira/browse/CXF-8875 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8817) Add support for Micrometer Observation
[ https://issues.apache.org/jira/browse/CXF-8817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8817: -- Fix Version/s: 3.5.7 3.6.2 4.0.3 > Add support for Micrometer Observation > -- > > Key: CXF-8817 > URL: https://issues.apache.org/jira/browse/CXF-8817 > Project: CXF > Issue Type: New Feature > Components: Core >Reporter: Marcin Grzejszczak >Priority: Major > Fix For: 3.5.7, 3.6.2, 4.0.3 > > > I'm a co-maintainer of Spring Cloud Sleuth and Micrometer projects (together > with Tommy Ludwig and Jonatan Ivanov). > [Micrometer Observation|https://micrometer.io/docs/observation] is coming as > part of the Micrometer 1.10 release and [Micrometer > Tracing|https://micrometer.io/docs/tracing] is a new project. The idea of > Micrometer Observation is that you instrument code once but you get multiple > benefits out of it - e.g. you can get tracing, metrics, logging or whatever > you see fit). > Since this project already supports Micrometer I was curious if there's > interest in adding Micrometer Observation support so that automatically (when > on classpath) except for metrics, spans could be created and tracing context > propagation could happen too. In other words metrics and tracing of this > project could be created + if there are Micrometer Observation compatible > projects, then they will join the whole graph (e.g. whole Spring Framework 6 > is, Apache Dubbo, Resilience4j etc.). > If there's interest in adding that feature, I can provide a PR. -- 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
[X] ./integration/jca/pom.xml
[X] ./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
[X] ./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
[X] ./rt/transports/http-netty/netty-client/pom.xml
[X] ./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
[X] ./integration/jca/pom.xml
[X] ./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
[X] ./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
[X] ./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]
[jira] [Updated] (CXF-8877) Get rid of EasyMock in cxf-rt-transports-http-netty-client
[ https://issues.apache.org/jira/browse/CXF-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8877: -- Fix Version/s: 3.5.7 3.6.2 4.0.3 > Get rid of EasyMock in cxf-rt-transports-http-netty-client > -- > > Key: CXF-8877 > URL: https://issues.apache.org/jira/browse/CXF-8877 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 3.5.7, 3.6.2, 4.0.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CXF-8877) Get rid of EasyMock in cxf-rt-transports-http-netty-client
[ https://issues.apache.org/jira/browse/CXF-8877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8877: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-rt-transports-http-netty-client > -- > > Key: CXF-8877 > URL: https://issues.apache.org/jira/browse/CXF-8877 > Project: CXF > Issue Type: Sub-task >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CXF-8858) Get rid of EasyMock in cxf-rt-frontend-js
[ https://issues.apache.org/jira/browse/CXF-8858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8858. --- Resolution: Fixed > Get rid of EasyMock in cxf-rt-frontend-js > - > > Key: CXF-8858 > URL: https://issues.apache.org/jira/browse/CXF-8858 > 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-8912) Remove xerces dependency and use the JDK's JAXP impl
[ https://issues.apache.org/jira/browse/CXF-8912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8912. --- Resolution: Fixed > Remove xerces dependency and use the JDK's JAXP impl > > > Key: CXF-8912 > URL: https://issues.apache.org/jira/browse/CXF-8912 > Project: CXF > Issue Type: Improvement > Components: Build system >Affects Versions: 4.0.2 >Reporter: Jim Ma >Assignee: Jim Ma >Priority: Major > Fix For: 4.0.3 > > > It looks the JDK's JAXP impl(after JDK11) is more updated and maintained then > the Apache Xerces. Move to use JDK's JAXP impl will reduce CXF's dependency > size and get the latest update for JAXP impl. -- 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
[X] ./integration/jca/pom.xml
[X] ./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
[X] ./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
[X] ./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
[X] ./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
[X] ./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
[X] ./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]
[jira] [Assigned] (CXF-8843) Get rid of EasyMock in cxf-integration-jca
[ https://issues.apache.org/jira/browse/CXF-8843?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8843: - Assignee: Andriy Redko > Get rid of EasyMock in cxf-integration-jca > -- > > Key: CXF-8843 > URL: https://issues.apache.org/jira/browse/CXF-8843 > 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] [Commented] (CXF-8911) Allow creating a custom CXFHttpAsyncResponseConsumer
[
https://issues.apache.org/jira/browse/CXF-8911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17752202#comment-17752202
]
Andriy Redko commented on CXF-8911:
---
This is interesting, looking into the problem briefly, using
CXFHttpAsyncResponseConsumerFactory and opening up the
CXFHttpAsyncResponseConsumer injection is probably not a good idea, there are
too many implementation details in there, I suspect the code would be
copy/pasted. From the other perspective, it seems like what you need is to
restore the context once the response is consumed, probably supplying
{color:#00}CXFResponseCallback is what you need. {color}
> Allow creating a custom CXFHttpAsyncResponseConsumer
>
>
> Key: CXF-8911
> URL: https://issues.apache.org/jira/browse/CXF-8911
> Project: CXF
> Issue Type: New Feature
>Reporter: Peter Palaga
>Priority: Major
>
> We recently got a [bug
> report|https://github.com/quarkiverse/quarkus-cxf/issues/947] in Quarkus CXF
> complaining about non-working context propagation with CXF HC5 client.
> The problem was that if the client is called in context of a Quarkus REST
> endpoint, whose vert.x thread has the request context setup properly, the
> request scoped beans are then not accessible e.g. from
> ContainerRequestFilters which run in in a different thread.
> To make it work, we would need wrap the creation of
> CXFHttpAsyncResponseConsumer in some code storing the context of the creation
> thread into a wrapping method that can then be executed by some other thread.
> I was able to do this by overriding some default classes. What I did can be
> seen around here:
> https://github.com/quarkiverse/quarkus-cxf/pull/950/files#diff-568a3d75d004f9f41c6130854755ebb2beae2f30308cc45aa98492d09bac2ecc
> This solution is by no means elegant and I wonder whether it would be
> feasible to implement some new API to allow creating custom
> CXFHttpAsyncResponseConsumers?
> Maybe we could introduce some kind of CXFHttpAsyncResponseConsumerFactory?
> I am quite new to CXF internals, so I'd be thankful for any hints how to
> proceed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
