Hi I think I have found the root cause of this issue. I have another copy of
cxf.xml is in my default class package so somehow cxf loads it by default
and this caused problem for my second application. Thanks


yong wrote:
> 
> Hi, I am seeing an issue with CXF running in JBoss4.0 which has a
> universal classloader (flat classloader). The first web app that uses cxf
> would deploy and run successfully but the second web app would deploy find
> but it would not be able to find the service by giving the error in the
> subject line.
> 
> The same cxf spring config for both web app is like this:
> 
> <beans xmlns="http://www.springframework.org/schema/beans";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:http-conf="http://cxf.apache.org/transports/http/configuration";
> xsi:schemaLocation="http://cxf.apache.org/transports/http/configuration
> http://cxf.apache.org/schemas/configuration/http-conf.xsd
> http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd";>
>     <!-- $Id: cxf.xml 17 2010-04-27 04:18:54Z eric.stephens $ -->
> 
>     <import resource="classpath:META-INF/cxf/cxf.xml"/>
>     <import resource="classpath:META-INF/cxf/cxf-extension-soap.xml"/>
>     <import resource="classpath:META-INF/cxf/cxf-servlet.xml"/>
> </beans>
> 
> I wonder if there is a singleton issue here. Can someone please shed some
> light on how to work around this issue? Thanks
> 

-- 
View this message in context: 
http://old.nabble.com/Can%27t-find-the-request-for-http%3A--sever%3Aport-wr-rest-report-ping-Observer-in-JBoss4.0-UCL-tp28439221p28439967.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to