[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=16763076#comment-16763076 ] Cesar Hernandez commented on TOMEE-2402: Can some of the Jira admins please assign this ticket to: [~mayens] > 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 >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (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=16763042#comment-16763042 ] James Meen commented on TOMEE-2467: --- Linking another issue that may also become a non-issue with this fix. > 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 > 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-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 ] James Meen updated TOMEE-2467: -- Issue Type: Bug (was: Improvement) > 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 > 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] [Commented] (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 commented on TOMEE-2467: --- 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 > 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] [Created] (TOMEE-2467) Improved CXFJAXRSFilter logic to fix non-CXF resource 404 responses
James Meen created TOMEE-2467: - Summary: 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: Improvement Components: TomEE Core Server Affects Versions: 8.0.0-M2 Reporter: James Meen 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)
[tomee] branch master updated (6459e30 -> ee96861)
This is an automated email from the ASF dual-hosted git repository.
jlmonteiro pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/tomee.git.
from 6459e30 TOMEE-2408. Metrics endpoint fix. Geronimo openapi impl bump
metrics spec bump
new e35d253 Start azure example. App and fat jar creation with TomEE
plugin
new 4795aa8 add web.xml to be able to use the war file
new 736bf94 rename application and improve documentation
new 28d2e82 tidy up properties
new d8c9312 explain why we don't use the azure plugin by default
new f0a31a4 fix port
new 502c281 use tomee webprofile
new 40d332e make sure source is java 8
new d7b5121 Merge remote-tracking branch 'upstream/master' into
azure-example
new 2fdf3e0 subdomain must be unique
new dbba981 azure bug
new ee96861 Merge pull request #378 from brunobat/azure-example
The 12119 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
examples/cloud-tomee-azure/README.adoc | 108 +
examples/cloud-tomee-azure/pom.xml | 129 +
.../main/java/org/superbiz/echo/EchoResource.java} | 20 ++--
.../src/main/webapp/WEB-INF/web.xml| 6 +-
examples/pom.xml | 1 +
5 files changed, 250 insertions(+), 14 deletions(-)
create mode 100644 examples/cloud-tomee-azure/README.adoc
create mode 100644 examples/cloud-tomee-azure/pom.xml
copy
examples/{multiple-arquillian-adapters/src/main/java/org/superbiz/SomeRest.java
=> cloud-tomee-azure/src/main/java/org/superbiz/echo/EchoResource.java} (79%)
copy examples/{rest-example-with-application =>
cloud-tomee-azure}/src/main/webapp/WEB-INF/web.xml (94%)
