[jira] [Commented] (CXF-8671) Support Jakarta EE 10
[ https://issues.apache.org/jira/browse/CXF-8671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860480#comment-17860480 ] Gary D. Gregory commented on CXF-8671: -- I am looking forward to 4.1.0 as well :) My latest experiment with 4.1.0-SNAPSHOT in our stack was successful :) > Support Jakarta EE 10 > - > > Key: CXF-8671 > URL: https://issues.apache.org/jira/browse/CXF-8671 > Project: CXF > Issue Type: Improvement >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 4.1.0 > > > 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 > ([https://repo1.maven.org/maven2/jakarta/platform/jakartaee-api-parent/10.0.0/jakartaee-api-parent-10.0.0.pom):] > * 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: > - Brave 6 > - OpenTelemetry 1.37.0+ > - Apache Tika 3.0.0 > ([https://github.com/apache/tika/releases/tag/3.0.0-BETA)] > - *[DONE]* UnboundID LDAP SDK for Java 7.0.0 > ([https://github.com/pingidentity/ldapsdk/releases/tag/7.0.0]) > - *[DONE]* Undertow 2.3.x > - *[DONE]* 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/)] > - *[DONE]* Hibernate 6.4 > ([https://in.relation.to/2023/11/23/orm-640-final/|https://in.relation.to/2023/08/31/orm-630/]) > - *[DONE]* Weld 5 > ([https://weld.cdi-spec.org/news/2022/04/29/weld-500Final/]) > - *[DONE]* Spring Boot 3.3 > ([https://github.com/spring-projects/spring-boot/releases/tag/v3.3.0|https://github.com/spring-projects/spring-boot/releases/tag/v3.1.0]) > - Spring Security 6.3 > ([https://github.com/spring-projects/spring-security/releases/tag/6.3.0|https://github.com/spring-projects/spring-security/releases/tag/6.1.0]) > - Micrometer 1.13 > ([https://github.com/micrometer-metrics/micrometer/releases/tag/v1.13.1|https://github.com/micrometer-metrics/micrometer/releases/tag/v1.11.0-M1]) > - Micrometer Tracing 1.3 > ([https://github.com/micrometer-metrics/tracing/releases/tag/v1.3.1)|https://github.com/micrometer-metrics/tracing/releases/tag/v1.1.4)] > - *[DONE]* Spring LDAP 3.2 > ([https://github.com/spring-projects/spring-ldap/releases/tag/3.2.0)|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]) > - Microprofile Config 3.1 > ([https://github.com/eclipse/microprofile-config/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] > > Migration Guide: > [https://cwiki.apache.org/confluence/display/CXF20DOC/4.1+Migration+Guide] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FEDIZ-257) Apache CXF Fediz Tomcat Plugin ver 1.6.1 does not work with Jakarta
[ https://issues.apache.org/jira/browse/FEDIZ-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860513#comment-17860513 ] Jamie Mark Goodyear commented on FEDIZ-257: --- I've started a work around for passing system properties into test cases. maven surefire plugin argLine -Dname=value appears to work when the failsafe settings do not apply. > Apache CXF Fediz Tomcat Plugin ver 1.6.1 does not work with Jakarta > --- > > Key: FEDIZ-257 > URL: https://issues.apache.org/jira/browse/FEDIZ-257 > Project: CXF-Fediz > Issue Type: Dependency upgrade > Components: Plugin >Affects Versions: 1.6.1 >Reporter: Mark >Priority: Major > Fix For: 1.6.1 > > > The following version of the fediz tomcat plugin was compiled with JDK 1.6 > and uses > https://cxf.apache.org/fediz-downloads.html > https://downloads.apache.org/cxf/fediz/1.6.1/ > If using version 1.6.1 with TomEE https://tomee.apache.org/download.html > I see errors encountering, java.lang.NoClassDefFoundError: > javax/xml/bind/JAXBException, that indicates the Java JAXB (Java Architecture > for XML Binding) API is not available in the runtime environment. This issue > is commonly encountered when running applications on Java versions 9 and > later, as JAXB was removed from the Java SE platform starting with Java 11. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (FEDIZ-257) Apache CXF Fediz Tomcat Plugin ver 1.6.1 does not work with Jakarta
[ https://issues.apache.org/jira/browse/FEDIZ-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860616#comment-17860616 ] Jamie Mark Goodyear commented on FEDIZ-257: --- Current blocker issue: System tests are not able to make connections to server, failing test case. Need to determine what is preventing services from listening/accepting connections. > Apache CXF Fediz Tomcat Plugin ver 1.6.1 does not work with Jakarta > --- > > Key: FEDIZ-257 > URL: https://issues.apache.org/jira/browse/FEDIZ-257 > Project: CXF-Fediz > Issue Type: Dependency upgrade > Components: Plugin >Affects Versions: 1.6.1 >Reporter: Mark >Priority: Major > Fix For: 1.6.1 > > > The following version of the fediz tomcat plugin was compiled with JDK 1.6 > and uses > https://cxf.apache.org/fediz-downloads.html > https://downloads.apache.org/cxf/fediz/1.6.1/ > If using version 1.6.1 with TomEE https://tomee.apache.org/download.html > I see errors encountering, java.lang.NoClassDefFoundError: > javax/xml/bind/JAXBException, that indicates the Java JAXB (Java Architecture > for XML Binding) API is not available in the runtime environment. This issue > is commonly encountered when running applications on Java versions 9 and > later, as JAXB was removed from the Java SE platform starting with Java 11. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (CXF-8980) JaxRS client - receive timeout not working since CXF 4.0.1
[ https://issues.apache.org/jira/browse/CXF-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko updated CXF-8980: -- Fix Version/s: 4.1.0 > JaxRS client - receive timeout not working since CXF 4.0.1 > -- > > Key: CXF-8980 > URL: https://issues.apache.org/jira/browse/CXF-8980 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 4.0.1, 4.0.2, 4.0.3 >Reporter: Emile de Weerd >Assignee: Andriy Redko >Priority: Major > Fix For: 3.5.9, 4.1.0, 4.0.5, 3.6.4 > > Attachments: cxf-4-receive-timeout-reproducer.zip > > > When the HTTP response returned is incomplete, i.e. a content-length header > is sent but the body sent is incomplete, since CXF 4.0.1 we can see that > there is no more a timeout and the following ProcessingException thrown. > It can be tested with this reproducer: > [^cxf-4-receive-timeout-reproducer.zip] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (CXF-8980) JaxRS client - receive timeout not working since CXF 4.0.1
[ https://issues.apache.org/jira/browse/CXF-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko reassigned CXF-8980: - Assignee: Andriy Redko > JaxRS client - receive timeout not working since CXF 4.0.1 > -- > > Key: CXF-8980 > URL: https://issues.apache.org/jira/browse/CXF-8980 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 4.0.1, 4.0.2, 4.0.3 >Reporter: Emile de Weerd >Assignee: Andriy Redko >Priority: Major > Fix For: 3.5.9, 4.0.5, 3.6.4 > > Attachments: cxf-4-receive-timeout-reproducer.zip > > > When the HTTP response returned is incomplete, i.e. a content-length header > is sent but the body sent is incomplete, since CXF 4.0.1 we can see that > there is no more a timeout and the following ProcessingException thrown. > It can be tested with this reproducer: > [^cxf-4-receive-timeout-reproducer.zip] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (CXF-8980) JaxRS client - receive timeout not working since CXF 4.0.1
[ https://issues.apache.org/jira/browse/CXF-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17860681#comment-17860681 ] Andriy Redko commented on CXF-8980: --- [~mederel] the issue seems to be related to HttpClient itself: - [https://bugs.openjdk.org/browse/JDK-8258397] - [https://bugs.openjdk.org/browse/JDK-8208693] - [https://bugs.openjdk.org/browse/JDK-8254223] Please consider switching to other client conduits if this particular case is critical for you, thank you. > JaxRS client - receive timeout not working since CXF 4.0.1 > -- > > Key: CXF-8980 > URL: https://issues.apache.org/jira/browse/CXF-8980 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 4.0.1, 4.0.2, 4.0.3 >Reporter: Emile de Weerd >Assignee: Andriy Redko >Priority: Major > Fix For: 3.5.9, 4.1.0, 4.0.5, 3.6.4 > > Attachments: cxf-4-receive-timeout-reproducer.zip > > > When the HTTP response returned is incomplete, i.e. a content-length header > is sent but the body sent is incomplete, since CXF 4.0.1 we can see that > there is no more a timeout and the following ProcessingException thrown. > It can be tested with this reproducer: > [^cxf-4-receive-timeout-reproducer.zip] -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (CXF-8980) JaxRS client - receive timeout not working since CXF 4.0.1
[ https://issues.apache.org/jira/browse/CXF-8980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andriy Redko resolved CXF-8980. --- Resolution: Workaround > JaxRS client - receive timeout not working since CXF 4.0.1 > -- > > Key: CXF-8980 > URL: https://issues.apache.org/jira/browse/CXF-8980 > Project: CXF > Issue Type: Bug > Components: JAX-RS >Affects Versions: 4.0.1, 4.0.2, 4.0.3 >Reporter: Emile de Weerd >Assignee: Andriy Redko >Priority: Major > Fix For: 3.5.9, 4.1.0, 4.0.5, 3.6.4 > > Attachments: cxf-4-receive-timeout-reproducer.zip > > > When the HTTP response returned is incomplete, i.e. a content-length header > is sent but the body sent is incomplete, since CXF 4.0.1 we can see that > there is no more a timeout and the following ProcessingException thrown. > It can be tested with this reproducer: > [^cxf-4-receive-timeout-reproducer.zip] -- This message was sent by Atlassian Jira (v8.20.10#820010)
