[ 
https://issues.apache.org/jira/browse/TOMEE-4643?focusedWorklogId=1033677&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1033677
 ]

ASF GitHub Bot logged work on TOMEE-4643:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 04/Aug/26 11:16
            Start Date: 04/Aug/26 11:16
    Worklog Time Spent: 10m 
      Work Description: jungm commented on PR #2877:
URL: https://github.com/apache/tomee/pull/2877#issuecomment-5178243543

   @rzo1 think its flaky but will check




Issue Time Tracking
-------------------

    Worklog Id:     (was: 1033677)
    Time Spent: 40m  (was: 0.5h)

> REST 3.1: no META-INF/services discovery for Feature/DynamicFeature
> -------------------------------------------------------------------
>
>                 Key: TOMEE-4643
>                 URL: https://issues.apache.org/jira/browse/TOMEE-4643
>             Project: TomEE
>          Issue Type: Bug
>            Reporter: Markus Jung
>            Assignee: Markus Jung
>            Priority: Major
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> TomEE does not scan {{META-INF/services}} for {{Feature}} and 
> {{DynamicFeature}} implementations. The REST 3.1 spec asks the runtime to 
> pick these up through the standard Java {{ServiceLoader}} mechanism at deploy 
> time. Because TomEE (through CXF) skips this step, a {{Feature}} or 
> {{DynamicFeature}} packaged this way never registers, and any behavior it 
> should add to the request or response pipeline never runs.
> Related upstream tracking: CXF-9005.
> This gap sits in TomEE's JAX-RS/CXF integration, not in the TCK or the test 
> harness.
> Related to TOMEE-4321, the open umbrella ticket for JAX-RS TCK failures.
> NOTE: this issue originally also covered a second, unrelated gap — a request 
> to an unmatched {{@Path}} returning HTTP 405 instead of 404. That has a 
> different root cause and has been split out to TOMEE-4659.
> h2. Steps to reproduce / TCK reference
> Suite: Jakarta RESTful Web Services 4.0 TCK 
> ({{jakarta.ws.rs:jakarta-restful-ws-tck:4.0.1}}).
> Feature/DynamicFeature discovery:
> * 
> {{ee/jakarta/tck/ws/rs/jaxrs31/spec/extensions/JAXRSClientIT.java#featureIsRegisteredTest}}
> * 
> {{ee/jakarta/tck/ws/rs/jaxrs31/spec/extensions/JAXRSClientIT.java#dynamicFeatureIsRegisteredTest}}
> Both are excluded via the surefire {{<excludes>}} block in 
> {{tck/jax-rs/jax-rs-tests/pom.xml}} (as a whole-class exclusion of 
> {{**/jaxrs31/spec/extensions/JAXRSClientIT.java}}, since surefire cannot 
> exclude individual methods). Remove that exclusion once fixed and the suite 
> should pass those tests.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to