[jira] [Commented] (TOMEE-2402) Add README.adoc to webservice-ws-with-resources-config/
[ https://issues.apache.org/jira/browse/TOMEE-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763936#comment-16763936 ] Cesar Hernandez commented on TOMEE-2402: Salomon PR is this one: [https://github.com/apache/tomee/pull/391] Is ready for review. > Add README.adoc to webservice-ws-with-resources-config/ > --- > > Key: TOMEE-2402 > URL: https://issues.apache.org/jira/browse/TOMEE-2402 > Project: TomEE > Issue Type: Sub-task >Reporter: David Blevins >Assignee: Salomon Mayengue >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Work started] (TOMEE-2402) Add README.adoc to webservice-ws-with-resources-config/
[ https://issues.apache.org/jira/browse/TOMEE-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on TOMEE-2402 started by Salomon Mayengue. --- > Add README.adoc to webservice-ws-with-resources-config/ > --- > > Key: TOMEE-2402 > URL: https://issues.apache.org/jira/browse/TOMEE-2402 > Project: TomEE > Issue Type: Sub-task >Reporter: David Blevins >Assignee: Salomon Mayengue >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TOMEE-2467) Improved CXFJAXRSFilter logic to fix non-CXF resource 404 responses
[ https://issues.apache.org/jira/browse/TOMEE-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated TOMEE-2467: -- Labels: pull-request-available (was: ) > Improved CXFJAXRSFilter logic to fix non-CXF resource 404 responses > --- > > Key: TOMEE-2467 > URL: https://issues.apache.org/jira/browse/TOMEE-2467 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 8.0.0-M2 >Reporter: James Meen >Priority: Major > Labels: pull-request-available > Fix For: 8.0.0-M3 > > > When a JAX-RS endpoints are added to a context, the CXF JAX-RS Filter is > added to the request filter chain automatically. This applies to both CXF > and non-CXF JAX-RS applications. > Until now, there was a problem with the CXF JAX-RS Filter where it processes > some requests treating them as CXF endpoints (e.g. JSPs and customer filter > mappings e.g. .abc file extensions). This produces a 404 Not Found response > even if the non-CXF resource did exist because CXF intercepted it but didn't > find a valid CXF resource. > This problem became much more prominent with the addition of MicroProfile > because the new extensions add REST endpoints to the application by default, > enabling the CXF JAX-RS Filter automatically - which breaks existing > functionality (producing 404s). > This improvement changes the CXF JAX-RS Filter to check if the requested > resource matches one of the valid CXF resource endpoints in the application. > If it does not, then the request is processed by TomEE without being > intercepted by CXF. Existing behaviour for valid CXF resources remains the > same. > This will enable all non-CXF based JAX-RS applications functionality to work > in TomEE, where in the past 404 errors would be experienced. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (TOMEE-2467) Improved CXFJAXRSFilter logic to fix non-CXF resource 404 responses
[ https://issues.apache.org/jira/browse/TOMEE-2467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763036#comment-16763036 ] James Meen edited comment on TOMEE-2467 at 2/8/19 8:57 PM: --- Linked PR 390 in github awaiting merge approval was (Author: jmeen): Linked PR 388 in github awaiting merge approval > Improved CXFJAXRSFilter logic to fix non-CXF resource 404 responses > --- > > Key: TOMEE-2467 > URL: https://issues.apache.org/jira/browse/TOMEE-2467 > Project: TomEE > Issue Type: Bug > Components: TomEE Core Server >Affects Versions: 8.0.0-M2 >Reporter: James Meen >Priority: Major > Labels: pull-request-available > Fix For: 8.0.0-M3 > > > When a JAX-RS endpoints are added to a context, the CXF JAX-RS Filter is > added to the request filter chain automatically. This applies to both CXF > and non-CXF JAX-RS applications. > Until now, there was a problem with the CXF JAX-RS Filter where it processes > some requests treating them as CXF endpoints (e.g. JSPs and customer filter > mappings e.g. .abc file extensions). This produces a 404 Not Found response > even if the non-CXF resource did exist because CXF intercepted it but didn't > find a valid CXF resource. > This problem became much more prominent with the addition of MicroProfile > because the new extensions add REST endpoints to the application by default, > enabling the CXF JAX-RS Filter automatically - which breaks existing > functionality (producing 404s). > This improvement changes the CXF JAX-RS Filter to check if the requested > resource matches one of the valid CXF resource endpoints in the application. > If it does not, then the request is processed by TomEE without being > intercepted by CXF. Existing behaviour for valid CXF resources remains the > same. > This will enable all non-CXF based JAX-RS applications functionality to work > in TomEE, where in the past 404 errors would be experienced. > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TOMEE-2390) Add README.adoc to multiple-tomee-arquillian/
[ https://issues.apache.org/jira/browse/TOMEE-2390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated TOMEE-2390: -- Labels: pull-request-available (was: ) > Add README.adoc to multiple-tomee-arquillian/ > - > > Key: TOMEE-2390 > URL: https://issues.apache.org/jira/browse/TOMEE-2390 > Project: TomEE > Issue Type: Sub-task >Reporter: David Blevins >Assignee: Mitja Jeseničnik Kotnik >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (TOMEE-2465) JDK 11 compatibility on Tomee 7.1.1
[ https://issues.apache.org/jira/browse/TOMEE-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore reassigned TOMEE-2465: - Assignee: Salomon Mayengue > JDK 11 compatibility on Tomee 7.1.1 > --- > > Key: TOMEE-2465 > URL: https://issues.apache.org/jira/browse/TOMEE-2465 > Project: TomEE > Issue Type: Bug >Affects Versions: 7.1.1 >Reporter: Salomon Mayengue >Assignee: Salomon Mayengue >Priority: Major > > Hello, > I started to use the TomEE 7.1.1-SNAPSHOT with JDK 11 and I still have issue > related to unSafeClass exception. Here is the complete stacktrace: > -- > 06-Feb-2019 10:42:03.955 INFO [pc04141-startStop-1] > org.apache.openejb.cdi.OpenEJBLifecycle.startApplication OpenWebBeans > Container has started, it took 223 ms. > 06-Feb-2019 10:42:03.974 SEVERE [Catalina-startStop-1] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke A child container failed > during start > java.util.concurrent.ExecutionException: > org.apache.catalina.LifecycleException: Failed to start component > [StandardEngine[Catalina].StandardHost[pc04141].StandardContext[/web.api]] > at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191) > at > org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:942) > at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:872) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1420) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1410) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:825) > Caused by: org.apache.catalina.LifecycleException: Failed to start component > [StandardEngine[Catalina].StandardHost[pc04141].StandardContext[/web.api]] > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167) > ... 6 more > Caused by: java.lang.NoClassDefFoundError: > org.apache.openejb.util.proxy.LocalBeanProxyFactory$Unsafe (initialization > failure) > at > java.base/java.lang.J9VMInternals.initializationAlreadyFailed(J9VMInternals.java:141) > at > org.apache.openejb.util.proxy.LocalBeanProxyFactory.createProxy(LocalBeanProxyFactory.java:137) > at > org.apache.openejb.util.proxy.LocalBeanProxyFactory.createProxy(LocalBeanProxyFactory.java:147) > at > org.apache.tomee.catalina.TomcatWebAppBuilder.eagerInitOfLocalBeanProxies(TomcatWebAppBuilder.java:1563) > at > org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1441) > at > org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1125) > at > org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:133) > at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94) > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5154) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > ... 6 more > -- > To fix this issue in my branch, I applied the same corrections of > - TOMEE-2272 > - + jdk 11 compatibility on LocalBeanProxyFactory.java (cf > 37e56343b92996ef3bed4535a2728c034f8d7725 of master branch) > So , in order to make 7.1.1 version fully compatible with JDK 11, do you plan > to report these changes in the 7.1.X branch? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (TOMEE-2402) Add README.adoc to webservice-ws-with-resources-config/
[ https://issues.apache.org/jira/browse/TOMEE-2402?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Gallimore reassigned TOMEE-2402: - Assignee: Salomon Mayengue > Add README.adoc to webservice-ws-with-resources-config/ > --- > > Key: TOMEE-2402 > URL: https://issues.apache.org/jira/browse/TOMEE-2402 > Project: TomEE > Issue Type: Sub-task >Reporter: David Blevins >Assignee: Salomon Mayengue >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (TOMEE-2465) JDK 11 compatibility on Tomee 7.1.1
[ https://issues.apache.org/jira/browse/TOMEE-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763527#comment-16763527 ] Salomon Mayengue edited comment on TOMEE-2465 at 2/8/19 12:03 PM: -- Can some of the Jira admins please assign this ticket to me : [~mayens] ? was (Author: mayens): Can some of the Jira admins please assign this ticket to me : [~mayens] ? * [|https://issues.apache.org/jira/secure/AddComment!default.jspa?id=13204826] > JDK 11 compatibility on Tomee 7.1.1 > --- > > Key: TOMEE-2465 > URL: https://issues.apache.org/jira/browse/TOMEE-2465 > Project: TomEE > Issue Type: Bug >Affects Versions: 7.1.1 >Reporter: Salomon Mayengue >Priority: Major > > Hello, > I started to use the TomEE 7.1.1-SNAPSHOT with JDK 11 and I still have issue > related to unSafeClass exception. Here is the complete stacktrace: > -- > 06-Feb-2019 10:42:03.955 INFO [pc04141-startStop-1] > org.apache.openejb.cdi.OpenEJBLifecycle.startApplication OpenWebBeans > Container has started, it took 223 ms. > 06-Feb-2019 10:42:03.974 SEVERE [Catalina-startStop-1] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke A child container failed > during start > java.util.concurrent.ExecutionException: > org.apache.catalina.LifecycleException: Failed to start component > [StandardEngine[Catalina].StandardHost[pc04141].StandardContext[/web.api]] > at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191) > at > org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:942) > at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:872) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1420) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1410) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:825) > Caused by: org.apache.catalina.LifecycleException: Failed to start component > [StandardEngine[Catalina].StandardHost[pc04141].StandardContext[/web.api]] > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167) > ... 6 more > Caused by: java.lang.NoClassDefFoundError: > org.apache.openejb.util.proxy.LocalBeanProxyFactory$Unsafe (initialization > failure) > at > java.base/java.lang.J9VMInternals.initializationAlreadyFailed(J9VMInternals.java:141) > at > org.apache.openejb.util.proxy.LocalBeanProxyFactory.createProxy(LocalBeanProxyFactory.java:137) > at > org.apache.openejb.util.proxy.LocalBeanProxyFactory.createProxy(LocalBeanProxyFactory.java:147) > at > org.apache.tomee.catalina.TomcatWebAppBuilder.eagerInitOfLocalBeanProxies(TomcatWebAppBuilder.java:1563) > at > org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1441) > at > org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1125) > at > org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:133) > at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94) > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5154) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > ... 6 more > -- > To fix this issue in my branch, I applied the same corrections of > - TOMEE-2272 > - + jdk 11 compatibility on LocalBeanProxyFactory.java (cf > 37e56343b92996ef3bed4535a2728c034f8d7725 of master branch) > So , in order to make 7.1.1 version fully compatible with JDK 11, do you plan > to report these changes in the 7.1.X branch? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TOMEE-2465) JDK 11 compatibility on Tomee 7.1.1
[ https://issues.apache.org/jira/browse/TOMEE-2465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16763527#comment-16763527 ] Salomon Mayengue commented on TOMEE-2465: - Can some of the Jira admins please assign this ticket to me : [~mayens] ? * [|https://issues.apache.org/jira/secure/AddComment!default.jspa?id=13204826] > JDK 11 compatibility on Tomee 7.1.1 > --- > > Key: TOMEE-2465 > URL: https://issues.apache.org/jira/browse/TOMEE-2465 > Project: TomEE > Issue Type: Bug >Affects Versions: 7.1.1 >Reporter: Salomon Mayengue >Priority: Major > > Hello, > I started to use the TomEE 7.1.1-SNAPSHOT with JDK 11 and I still have issue > related to unSafeClass exception. Here is the complete stacktrace: > -- > 06-Feb-2019 10:42:03.955 INFO [pc04141-startStop-1] > org.apache.openejb.cdi.OpenEJBLifecycle.startApplication OpenWebBeans > Container has started, it took 223 ms. > 06-Feb-2019 10:42:03.974 SEVERE [Catalina-startStop-1] > jdk.internal.reflect.NativeMethodAccessorImpl.invoke A child container failed > during start > java.util.concurrent.ExecutionException: > org.apache.catalina.LifecycleException: Failed to start component > [StandardEngine[Catalina].StandardHost[pc04141].StandardContext[/web.api]] > at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122) > at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:191) > at > org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:942) > at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:872) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1420) > at > org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1410) > at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) > at > java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) > at > java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) > at java.base/java.lang.Thread.run(Thread.java:825) > Caused by: org.apache.catalina.LifecycleException: Failed to start component > [StandardEngine[Catalina].StandardHost[pc04141].StandardContext[/web.api]] > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167) > ... 6 more > Caused by: java.lang.NoClassDefFoundError: > org.apache.openejb.util.proxy.LocalBeanProxyFactory$Unsafe (initialization > failure) > at > java.base/java.lang.J9VMInternals.initializationAlreadyFailed(J9VMInternals.java:141) > at > org.apache.openejb.util.proxy.LocalBeanProxyFactory.createProxy(LocalBeanProxyFactory.java:137) > at > org.apache.openejb.util.proxy.LocalBeanProxyFactory.createProxy(LocalBeanProxyFactory.java:147) > at > org.apache.tomee.catalina.TomcatWebAppBuilder.eagerInitOfLocalBeanProxies(TomcatWebAppBuilder.java:1563) > at > org.apache.tomee.catalina.TomcatWebAppBuilder.startInternal(TomcatWebAppBuilder.java:1441) > at > org.apache.tomee.catalina.TomcatWebAppBuilder.configureStart(TomcatWebAppBuilder.java:1125) > at > org.apache.tomee.catalina.GlobalListenerSupport.lifecycleEvent(GlobalListenerSupport.java:133) > at > org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:94) > at > org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5154) > at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150) > ... 6 more > -- > To fix this issue in my branch, I applied the same corrections of > - TOMEE-2272 > - + jdk 11 compatibility on LocalBeanProxyFactory.java (cf > 37e56343b92996ef3bed4535a2728c034f8d7725 of master branch) > So , in order to make 7.1.1 version fully compatible with JDK 11, do you plan > to report these changes in the 7.1.X branch? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
