cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andriy Redko (JIRA)" <>
Subject [jira] [Commented] (CXF-6132) Provide JAX-RS ServletContextInitializer
Date Tue, 20 Jan 2015 01:41:35 GMT


Andriy Redko commented on CXF-6132:

Hi Sergey,

I have started to think about the implementation and here are some very rough thoughts from
my side:
 - I agree with you, we probably should have a separate module for ServletContextInitializer
implementation, do you have any suggestion where to put it and how to call it?
 - the ServletContextInitializer implementation will declare itself as @HandlesTypes( Application.class
), the container should discover those classes automatically (it is more reliable way to determine
the JAX-RS application, I think @ApplicationPath is not a mandatory annotation) 
 - having the application class instance, we could check the getSingletons() / getResources()
to check if application sets up everything (as you described in previous comment)
 - if not, we probably could go with auto-discovery or ask developers to subclass the ServletContextInitializer
and specify providers / features / resource classes.

What do you think? Does it make sense to you?

> Provide JAX-RS ServletContextInitializer 
> -----------------------------------------
>                 Key: CXF-6132
>                 URL:
>             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]
> [2]

This message was sent by Atlassian JIRA

View raw message