[
https://issues.apache.org/jira/browse/CXF-1072?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538362
]
Damien B commented on CXF-1072:
-------------------------------
Even when removing the Spring dependency-hardcoding, the CXFServlet is doomed
to fail: servletTransportFactory is instanciated after the creation of the
ServletController, which always leads to a NPE.
> CXFServlet can't be configured without using Spring.
> ----------------------------------------------------
>
> Key: CXF-1072
> URL: https://issues.apache.org/jira/browse/CXF-1072
> Project: CXF
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.0.1
> Environment: Tomcat v5.5.17
> Reporter: Corey Puffalt
>
> CXFServlet appears to be designed to allow configuration without using Spring
> via the loadBusNoConfig() method called from init() but although reflection
> is used to test for the existence of the Spring ApplicationContext class,
> elsewhere in the code there is an instance variable of type
> ApplicationContext (and other spring types.) This means it's impossible to
> instantiate CXFServlet without Spring on the classpath and if you add Spring
> to the classpath so you can instantiate CXFServlet then it will only attempt
> to configure itself via Spring.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
