JAXRS: RegEx Jersey vs. CXF (2.5.2)

Hi,

I have another issue within compatibility between Jersey and CXF and maybe
you can give me a hint. The issue is with the following URL pattern where
CXF doesn't dispatch to the expected handler:

http://localhost:8810/test/test.svc/categories(1)/products

The relevant code snippet is a resource class and a sub resource class:

@Path("{entitySetName}{id: \\(.+?\\)}")
public class EntityRequestResource {

  @Path("{navProp: .+}")
  public PropertyRequestResource getNavProperty() {
    return new PropertyRequestResource();
  }
}


public class PropertyRequestResource {
  @GET
  @Produces({
    ODataConstants.APPLICATION_ATOM_XML_CHARSET_UTF8,
    ODataConstants.TEXT_JAVASCRIPT_CHARSET_UTF8,
    ODataConstants.APPLICATION_JAVASCRIPT_CHARSET_UTF8 })
  public Response getNavProperty() {...}
}

The complete WADL file is checked into a source repository and is
accessible at [1]. [2] is the corresponding Jersey generated WADL file of
the same code. With Jersey it doesn't fail. [3] is an example maven
project with has a failing JUnit test isolating the problem. [4] is the
fine trace of CXF that doesn't find a matching method.

Any hint how to get this fixed is welcome. Thanks in advance.

Regards,
Stephan


[1]
https://bitbucket.org/sklevenz/example/src/ecc3183d5976/org.example.core/sr" rel="nofollow" target="_blank">https://bitbucket.org/sklevenz/exampl...g.example.core/sr
c/test/resources/wadl.cxf.xml
[2]
https://bitbucket.org/sklevenz/example/src/ecc3183d5976/org.example.core/sr" rel="nofollow" target="_blank">https://bitbucket.org/sklevenz/exampl...g.example.core/sr
c/test/resources/wadl.jersey.xml
[3] https://bitbucket.org/sklevenz/example
[4] CXF Trace:
2012-02-07 17:38:09,744 INFO  [main]
org.example.test.compatibility.OData4JCompatibilityTest:
******************************************************************
2012-02-07 17:38:09,745 INFO  [main]
org.example.test.compatibility.OData4JCompatibilityTest: Activated Server
Type = CXF
2012-02-07 17:38:09,745 INFO  [main]
org.example.test.compatibility.OData4JCompatibilityTest:
******************************************************************
2012-02-07 17:38:09,746 INFO  [main]
org.example.test.compatibility.OData4JCompatibilityTest: