Not to reply to my own post, but I finally figured things out. This is the
way I am understanding things: The CXFServlet and the CXFNonSpringServlet
maintain a collection of services published in their context, or on their
bus. So if I published an endpoint in the context of a
ServletContextListener, or some other servlet, it makes sense that the
CXFServlet or CXFNonSpringServlet would know nothing about it, and thus
could not route requests to it. The key was here:
http://cxf.apache.org/docs/servlet-transport.html. The bottom line is that I
subclassed the CXFNonSpringServlet, and published my STS-instance-publishing
web-service in the over-ridden loadBus method:
@Override
public void loadBus(ServletConfig servletConfig) {
super.loadBus(servletConfig);
Bus bus = getBus();
BusFactory.setDefaultBus(bus);
Endpoint.publish("/sts_publish", new STSPublishImpl());
}
My web.xml specifies my CXFNonSpringServlet subclass. My
STS-instance-publishing service then publishes no problem, and any STS
instance published by calling this web-service is also happily exposed and
consumable relative to the servlet-mapping corresponding to my
CXFNonSpringServlet subclass.
Eureka.
--
View this message in context:
http://cxf.547215.n5.nabble.com/JaxWsServerFactoryBean-without-Spring-tp5724258p5724325.html
Sent from the cxf-user mailing list archive at Nabble.com.
