[
https://issues.apache.org/jira/browse/CXF-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14293374#comment-14293374
]
Sergey Beryozkin commented on CXF-6132:
---------------------------------------
Hi Andriy
The whole point of CXF-5702 was to make that change to
CxfNonSpringJaxrsServlet, you can check the difference, I had to revert a
servlet change given that a system test started failing. Basically if
CxfNonSpringJaxrsServlet is loaded it means ApplicationPath is ignored by
default (the parameter is null) which is a spec compliance thing (the
preference of a servlet path over the application path). The side-effect is
that if people do want to use ApplicationPath when loading Application with
CxfNonSpringJaxrsServlet then they need to explicitly set that property with a
value false. Hope it clarifies it. It can be confusing all right :-)
Many thanks for getting the initial code for the initializer in
Thanks, Sergey
> Provide JAX-RS ServletContextInitializer
> -----------------------------------------
>
> Key: CXF-6132
> URL: https://issues.apache.org/jira/browse/CXF-6132
> Project: CXF
> Issue Type: New Feature
> Components: JAX-RS
> Reporter: Sergey Beryozkin
> Assignee: Andriy Redko
> Fix For: 3.0.4, 3.1.0
>
>
> This will offer an advanced support for the auto-discovery of JAX-RS
> Application, root resources and providers in OSGI in combination with
> pax-web-jetty.
> Options:
> - dynamically register the implementation as OSGI service
> - ship a static implementation
> [1]
> https://github.com/ops4j/org.ops4j.pax.web/blob/master/pax-web-jetty/src/main/java/org/ops4j/pax/web/service/jetty/internal/JettyServerWrapper.java#L303
> [2]
> http://docs.oracle.com/javaee/7/api/javax/servlet/ServletContainerInitializer.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
