Peter Hendry wrote:
> I'll try to explain what I see as the issue. An application has a
> "deployment" model and it has an "endpoint" model. The RI is merging the
> 2 when deploying in servlets. It is saying that just because an
> application is deployed as a servlet it will only want to use servlet
> endpoints. This is not the case. Consider an example application (we
> have this at a customer)
I understand what you mean. We went through the same thought process.
In your terminology, the JAX-WS RI does not have any deployment model.
WSServletContextListener is not a deployment model. It's just a
bootstrap mechanism for servlet endpoint.
> I've started to play with the spring integration project to see if I can
> make that work around this.
In the spring integration project, Spring serves as the deployment
model, and it's capable of bootstrapping any endpoint model anyone does
as extensions.
--
Kohsuke Kawaguchi
Sun Microsystems kohsuke.kawaguchi_at_sun.com