Any chance you could take a hello world thing and create a sample of this 
issue?  I really don't know what would cause this, but if we can reproduce, we 
can at least debug it.

Dan


On Thursday 11 November 2010 8:26:17 pm Conficio wrote:
> Hi there,
> I want to use two CXFServlets in my web.xml, one for public and one for
> private services.
> 
> I tried to define
> 
> 
>   <servlet>
>     <servlet-name>CXFPrivateServlet</servlet-name>
>     <servlet-class>
>         org.apache.cxf.transport.servlet.CXFServlet
>     </servlet-class>
>     <init-param>
>       <param-name>config-location</param-name>
>       <param-value>/WEB-INF/private.xml</param-value>
>     </init-param>
>     <load-on-startup>1</load-on-startup>
>   </servlet>
> 
>   <servlet-mapping>
>     <servlet-name>CXFPrivateServlet</servlet-name>
>     <url-pattern>/services/private/*</url-pattern>
>   </servlet-mapping>
> <servlet>
>     <servlet-name>CXFPubicServlet</servlet-name>
>     <servlet-class>
>         org.apache.cxf.transport.servlet.CXFServlet
>     </servlet-class>
>     <init-param>
>       <param-name>config-location</param-name>
>       <param-value>/WEB-INF/public.xml</param-value>
>     </init-param>
>     <load-on-startup>1</load-on-startup>
>   </servlet>
> 
>   <servlet-mapping>
>     <servlet-name>CXFPublicServlet</servlet-name>
>     <url-pattern>/services/public/*</url-pattern>
>   </servlet-mapping>
> 
> 
> This does not seem to work. If I have two servlets like this it loops in
> the service endpoint publishing.
> 
> If I only define a single config-location and servler-mapping, then the
> servlet endpoints are published in the startup, but the servlet does not
> serve the WSDL or overview page.
> 
> Is there a better way to achieve that?
> 
> K<o>
> P.S.: This is all part of a spring configured container. When I define a
> global include of the endpoint beans and a CXFServlet w/o any
> config-location, then the services are deployed, but all under a single
> URI.

-- 
Daniel Kulp
[email protected]
http://dankulp.com/blog

Reply via email to