[
https://issues.apache.org/jira/browse/CXF-6132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14291728#comment-14291728
]
Sergey Beryozkin commented on CXF-6132:
---------------------------------------
Hi Andriy
Great to know you have something working already :-).
Right, ignoreParam issue is actually not caused by my latest commit, see
https://issues.apache.org/jira/browse/CXF-5702.
Re the discovery of the internal Application - would making it abstract and
creating a local instantiation in the constructor help ? I guess otherwise just
excluding the specific internal class would be fine too.
Re the separate module. In the early 2.0 TCK test that I worked with most of
the tests do depend on concrete servlets but few of tests rely on this
introspection feature. Meaning the endpoints with and without web.xml should be
supported at the same time. Is it possible to update the initilaizer somehow
and check if servlet context already has servlet registrations and if yes then
just skip the processing ?
Having a sep module is likely ro be the best solution because we do not want to
have the servlet containers use the initializer if we do not want to (it will
slow down the process after all), but IMHO the cxf endpoints with or without
web.xml should work at the same time. May be "rt-rs-http-sci", more cryptic but
also more specific :-) ? Every new module just adds to the rather high overall
number of CXF modules but I'm not sure we have an alternative in this case...
Please experiment with blocking the processing first, and then if Dan does not
object, please add a new module
Many 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)
