cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <>
Subject [jira] [Commented] (CXF-4938) Setting RuntimeDelegate instance in CXFNonSpringJaxrsServlet is too aggresive
Date Wed, 03 Apr 2013 08:57:16 GMT


Sergey Beryozkin commented on CXF-4938:

I started some work on minimizing the dependency of the runtime on RuntimeDelegate in the
first place, however as far as I recall this initializer was added on the request to bypass
some issues in some of the OSGI environments where CXF RuntimeDelegate could not be located.
May be I can introduce CXFRuntimeDelegateServlet which extends CXFNonSpringJaxrsServlet and
this one will do a static initializer, not sure yet...
> Setting RuntimeDelegate instance in CXFNonSpringJaxrsServlet is too aggresive
> -----------------------------------------------------------------------------
>                 Key: CXF-4938
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.4.10
>         Environment: JBoss AS 7.1
>            Reporter: Marek Winkler
>            Priority: Critical
> Setting RuntimeDelegate instance in CXFNonSpringJaxrsServlet breaks the ability to use
CXF, bundled in a WAR application, along with other JAX-RS providers for other applications
deployed on the same application server.
> The problem occurs for instance on JBoss AS 7.1, when one application uses CXF, while
the other uses RestEasy. It occurs after upgrading from 2.4.8 to 2.4.10 (I can see that the
static initializer had been introduced there).
> Could you consider changing the static initializer in CXFNonSpringJaxrsServlet to something

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message