[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001997#comment-17001997
]
Andriy Redko commented on CXF-8134:
---
I have just quickly picked one of our JAX-RS samples, a few examples are
immediately showing up:
* jakarta.annotation-api and javax.annotation-api
* jakarta.validation-api and validation-api
* jakarta.activation-api and javax.activation-api (not a the picture but in
dependency graph)
* ...
!image-2019-12-22-16-34-44-435.png|width=414,height=436!
There are surely more to pin point.
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: image-2019-12-22-16-34-24-327.png,
> image-2019-12-22-16-34-31-499.png, image-2019-12-22-16-34-44-435.png
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko updated CXF-8134:
--
Attachment: image-2019-12-22-16-34-31-499.png
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: image-2019-12-22-16-34-24-327.png,
> image-2019-12-22-16-34-31-499.png, image-2019-12-22-16-34-44-435.png
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko updated CXF-8134:
--
Attachment: image-2019-12-22-16-34-24-327.png
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: image-2019-12-22-16-34-24-327.png,
> image-2019-12-22-16-34-31-499.png, image-2019-12-22-16-34-44-435.png
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andriy Redko updated CXF-8134:
--
Attachment: image-2019-12-22-16-34-44-435.png
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
> Attachments: image-2019-12-22-16-34-24-327.png,
> image-2019-12-22-16-34-31-499.png, image-2019-12-22-16-34-44-435.png
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001993#comment-17001993
]
Dennis Kieselhorst commented on CXF-8134:
-
Well I share that concern but looking at our sample projects I haven't noticed
any duplicate dependencies.
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17001992#comment-17001992
]
Andriy Redko commented on CXF-8134:
---
Hi [~deki] ,
I think the main concern was not regarding CXF not working with Spring Boot but
the amount of "duplicate" dependencies which are now scattered between "old"
(javax / sun / ...) and "new" (jakarta) artifacts. The CXF-7910 should have
helped us to address that. I am not sure we should have rushed with Spring Boot
2.2 upgrade before finalizing the grounding work.
Best Regards,
Andriy Redko
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CXF-8134) Upgrade to Spring Boot 2.2
[
https://issues.apache.org/jira/browse/CXF-8134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst resolved CXF-8134.
-
Resolution: Fixed
Hi [~reta],
we should definitely get the Jakarta dependency changes done but the newest
Spring Boot version still works with CXF so I did the upgrade. Let me know if I
am missing something.
Best,
Dennis
> Upgrade to Spring Boot 2.2
> --
>
> Key: CXF-8134
> URL: https://issues.apache.org/jira/browse/CXF-8134
> Project: CXF
> Issue Type: Improvement
>Affects Versions: 3.4.0
>Reporter: Andriy Redko
>Assignee: Andriy Redko
>Priority: Major
> Fix For: 3.4.0
>
>
> Spring Boot 2.2 has just been released:
> * [https://spring.io/blog/2019/10/16/spring-boot-2-2-0]
> *
> [https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-2.2-Release-Notes]
> One of the most important and impactful changes are related to *Jakarta EE
> dependencies*:
>
> {quote}Where possible, we have moved from Java EE dependencies with a
> {{javax.**}} group ID to the equivalent Jakarta EE dependencies with a
> {{jakarta.}} group ID in Spring Boot’s starters. Dependency management for
> the Jakarta EE API dependencies has been added alongside the existing
> dependency management for the Java EE API dependencies. The dependency
> management for the Java EE API dependencies will be removed in the future and
> all users are encouraged to move to the Jakarta EE API dependencies.
> As part of the Java EE to Jakarta EE migration, two dependencies have changed
> artifact ID in their latest maintenance releases. {{com.sun.mail:javax.mail}}
> is now {{com.sun.mail:jakarta.mail}} and {{org.glassfish:javax.el}} is now
> {{org.glassfish:jakarta.el}}. In the unlikely event that you were using
> either of these dependencies directly, please update your {{pom.xml}} or
> {{build.gradle}} accordingly.
> {quote}
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Resolved] (CXF-8165) Upgrade to Spring Framework 5.2.x and Spring Security 5.2.x
[ https://issues.apache.org/jira/browse/CXF-8165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst resolved CXF-8165. - Resolution: Fixed > Upgrade to Spring Framework 5.2.x and Spring Security 5.2.x > --- > > Key: CXF-8165 > URL: https://issues.apache.org/jira/browse/CXF-8165 > Project: CXF > Issue Type: Task >Affects Versions: 3.4.0 >Reporter: Andriy Redko >Assignee: Andriy Redko >Priority: Major > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (CXF-8173) Illegal reflective access to field java.util.concurrent.ThreadPoolExecutor.mainLock
[
https://issues.apache.org/jira/browse/CXF-8173?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst updated CXF-8173:
Fix Version/s: 3.3.5
3.4.0
> Illegal reflective access to field
> java.util.concurrent.ThreadPoolExecutor.mainLock
> ---
>
> Key: CXF-8173
> URL: https://issues.apache.org/jira/browse/CXF-8173
> Project: CXF
> Issue Type: Bug
>Affects Versions: 3.3.4
>Reporter: Jimmy Praet
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 3.4.0, 3.3.5
>
>
> I get the following warning on JDK 11:
> {code:java}
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.cxf.common.util.ReflectionUtil$11
> (file:/D:/mvn_repo/org/apache/cxf/cxf-core/3.3.4/cxf-core-3.3.4.jar) to field
> java.util.concurrent.ThreadPoolExecutor.mainLock
> WARNING: Please consider reporting this to the maintainers of
> org.apache.cxf.common.util.ReflectionUtil$11
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future
> release{code}
> With --illegal-access=debug:
> {code:java}
> WARNING: Illegal reflective access by
> org.apache.cxf.common.util.ReflectionUtil$11
> (file:/D:/mvn_repo/org/apache/cxf/cxf-core/3.3.4/cxf-core-3.3.4.jar) to field
> java.util.concurrent.ThreadPoolExecutor.mainLock
> at org.apache.cxf.common.util.ReflectionUtil$11.run(ReflectionUtil.java:184)
> at org.apache.cxf.common.util.ReflectionUtil$11.run(ReflectionUtil.java:182)
> at java.base/java.security.AccessController.doPrivileged(Native Method)
> at
> org.apache.cxf.common.util.ReflectionUtil.setAccessible(ReflectionUtil.java:182)
> at
> org.apache.cxf.workqueue.AutomaticWorkQueueImpl.getExecutor(AutomaticWorkQueueImpl.java:206)
> at
> org.apache.cxf.workqueue.AutomaticWorkQueueImpl.execute(AutomaticWorkQueueImpl.java:425)
> at
> org.apache.cxf.workqueue.AutomaticWorkQueueImpl.execute(AutomaticWorkQueueImpl.java:455)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponseOnWorkqueue(HTTPConduit.java:1233)
> at
> org.apache.cxf.transport.http.URLConnectionHTTPConduit$URLConnectionWrappedOutputStream.handleResponseAsync(URLConnectionHTTPConduit.java:333)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleResponse(HTTPConduit.java:1572)
> at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.close(HTTPConduit.java:1371)
> at
> org.apache.cxf.ext.logging.LoggingOutputStream.postClose(LoggingOutputStream.java:53)
> at org.apache.cxf.io.CachedOutputStream.close(CachedOutputStream.java:228)
> at org.apache.cxf.transport.AbstractConduit.close(AbstractConduit.java:56)
> at org.apache.cxf.transport.http.HTTPConduit.close(HTTPConduit.java:671)
> at
> org.apache.cxf.interceptor.MessageSenderInterceptor$MessageSenderEndingInterceptor.handleMessage(MessageSenderInterceptor.java:63)
> at
> org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:308)
> at org.apache.cxf.endpoint.ClientImpl.doInvoke(ClientImpl.java:530)
> at org.apache.cxf.endpoint.ClientImpl.invoke(ClientImpl.java:434)
> at org.apache.camel.component.cxf.CxfProducer.process(CxfProducer.java:117)
> at
> be.fgov.kszbcss.camel.support.component.soap.SoapCallProducer.process(SoapCallProducer.java:93)
> at org.apache.camel.processor.SendProcessor.process(SendProcessor.java:134)
> at
> org.apache.camel.processor.errorhandler.RedeliveryErrorHandler$RedeliveryState.run(RedeliveryErrorHandler.java:476)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor$Worker.schedule(DefaultReactiveExecutor.java:185)
> at
> org.apache.camel.impl.engine.DefaultReactiveExecutor.scheduleMain(DefaultReactiveExecutor.java:59)
> at org.apache.camel.processor.Pipeline.process(Pipeline.java:87)
> at
> org.apache.camel.processor.CamelInternalProcessor.process(CamelInternalProcessor.java:228)
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.asyncInvoke(CxfConsumer.java:182)
> at
> org.apache.camel.component.cxf.CxfConsumer$CxfConsumerInvoker.invoke(CxfConsumer.java:158)
> at
> org.apache.cxf.interceptor.ServiceInvokerInterceptor$1.run(ServiceInvokerInterceptor.java:59)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> {code}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Updated] (CXF-8183) JDK 9+ Illegal reflective access caused in AutomaticWorkQueueImpl
[
https://issues.apache.org/jira/browse/CXF-8183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Kieselhorst updated CXF-8183:
Fix Version/s: 3.3.5
3.4.0
> JDK 9+ Illegal reflective access caused in AutomaticWorkQueueImpl
> -
>
> Key: CXF-8183
> URL: https://issues.apache.org/jira/browse/CXF-8183
> Project: CXF
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.3.4
> Environment: OpenJDK 11 inside docker container
> {{fabric8/java-centos-openjdk11-jre}}
>Reporter: Peter Schulz
>Assignee: Freeman Yue Fang
>Priority: Major
> Fix For: 3.4.0, 3.3.5
>
>
> We use CXF for SOAP with {{cxf-rt-transports-http-hc-3.3.4.jar}} (Async
> HTTP) and do get the following warning:
> {code:none}
> WARNING: Illegal reflective access by
> org.apache.cxf.common.util.ReflectionUtil$11
> (file:/Users/peterschulz/.m2/repository/org/apache/cxf/cxf-core/3.3.4/cxf-core-3.3.4.jar)
> to field java.util.concurrent.ThreadPoolExecutor.mainLock
> WARNING: Please consider reporting this to the maintainers of
> org.apache.cxf.common.util.ReflectionUtil$11
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future
> release{code}
>
> {{org.apache.cxf.workqueue.AutomaticWorkQueueImpl}} line 206 and/or 439
> {code:java}
> Field f = ThreadPoolExecutor.class.getDeclaredField("mainLock");
> ReflectionUtil.setAccessible(f);
> l = (ReentrantLock)f.get(executor);
> /*...*/
> ReflectionUtil.setAccessible(addWorkerMethod).invoke(executor,
> addWorkerArgs);{code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
