cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kou, Zhi Qiang (JIRA)" <>
Subject [jira] [Created] (CXF-5702) CXF 3.0 implementation issue with JAX-RS
Date Fri, 18 Apr 2014 03:53:14 GMT
Kou, Zhi Qiang created CXF-5702:

             Summary: CXF 3.0 implementation issue with JAX-RS
                 Key: CXF-5702
             Project: CXF
          Issue Type: Bug
          Components: JAX-RS
    Affects Versions: 3.0.0-milestone2
         Environment: Windows
            Reporter: Kou, Zhi Qiang
            Priority: Blocker

It seems CXF JAX-RS implementation has something wrong with the relationship between defined
servlet-mapping and the value of ApplicationPath annotation.

>From JSR-339 spec, section 2.3.2: If the Application subclass is annotated with @ApplicationPath,
implementations are REQUIRED to use the value of this annotation appended with ”/*” to
define a mapping for the added server. Otherwise, the application MUST be packaged with a
web.xml that specifies a servlet mapping.

Also from ApplicationPath javadoc:
Identifies the application path that serves as the base URI for all resource URIs provided
by Path. May only be applied to a subclass of Application. When published in a Servlet container,
the value of the application path may be overridden using a servlet-mapping element in the

>From above information, if both servlet-mapping in web.xml and ApplicationPath has value,
only one of them should be used as the base URI, and it should be the value of servlet-mapping
in web.xml.

In my application, my web.xml looks like below. There are two servlet defined, each for one
jaxrs application. And the servlet-mapping values are defined as "/first/*" and "/second/*".

And in my application classes:

public class UserDemoApplication extends {

public class GroupDemoApplication extends {

So in this case according to spec and javadoc, "/first/*" and "/second/*" should be used as
the base URI, but not the "userdemo" and "groupdemo".

But in the real case I can only access the resources via URLs:


However if I implement the same application using Jersey RI libs, I can access my resources
via URLs:

My feeling is Jersey RI implementation is correct behavior according to SPEC and JavaDoc.
Please let me know if my understanding is correct or not.

Any help is highly appreciated! Thank you!

This message was sent by Atlassian JIRA

View raw message