[ 
https://issues.apache.org/jira/browse/CXF-3420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Daniel Kulp resolved CXF-3420.
------------------------------

       Resolution: Cannot Reproduce
    Fix Version/s:     (was: NeedMoreInfo)
                   Invalid
         Assignee: Daniel Kulp


Closing this as no testcase could be provided after a month and unable to 
reproduce.

> WEB-INF/cxf-servlet.xml causing cross application issues
> --------------------------------------------------------
>
>                 Key: CXF-3420
>                 URL: https://issues.apache.org/jira/browse/CXF-3420
>             Project: CXF
>          Issue Type: Bug
>          Components: Configuration
>         Environment: CXF 2.1.3, Jboss 4.2.3, JDK 1.6
>            Reporter: Yogesh
>            Assignee: Daniel Kulp
>             Fix For: Invalid
>
>
> We have two applications
> ProjectA
> ProjectB
> ProjectA contains cxf-servlet.xml file inside WEB-INF directory while 
> ProjectB doesnt contain this file. For Project B, the configuration for 
> loading webservices are done via separate file and the path for same is 
> configured in WEB-INF file.
> When both the applications are deployed, it deploys ProjectA first and then 
> starts deploying ProjectB
> While deploying ProjectB, it logs following statement
> 10:52:43,567 ERROR [STDERR] Mar 25, 2011 10:52:43 AM 
> org.apache.cxf.transport.servlet.CXFServlet loadAdditionalConfig
> INFO: Build endpoints from config-location: /WEB-INF/cxf-servlet.xml
> and throws error as classnotfoundexception.
> It is strange to see that there is no cxf-servlet.xml file inside ProjectB 
> and still CXF tries to load it. Dont know why, but somehow it is getting the 
> file defined in ProjectA and starts loading those beans inside ProjectB.
> Can you let us know what could be the reason behind such cross-reference 
> files getting loaded by CXF?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to