Re: [jetty-user] Jetty JAX-WS 2.2 SPI implementation?
Jesse McConnell <[email protected]> Fri, 1 Jul 2011 17:28:40 -0500
| Newsgroups | gmane.comp.java.jetty.support |
|---|---|
| Message-ID | <CAPHPUs+hqYr57Mh7r_rMzgpFFehSLY9RcvokJ1qiLSeTcW=xgw@mail.gmail.com> |
Aaron, this is cool, I'll give it some thought and look closer at the jax-ws stuff over the weekend and try and come back with some ideas on sprucing it up since your interested. cheers, jesse -- jesse mcconnell [email protected] On Fri, Jul 1, 2011 at 07:51, Jesse McConnell <[email protected]>wrote: > >> I went ahead and created an implementation >> >> https://github.com/aaronanderson/jetty-jaxws-http-spi >> >> I can also clean it up as needed if it would make a good official >> contribution. >> >> > cool, on my list of things to take a look at, this would be a nice addition > > >> One of the use cases I would like to support is the dynamic addition and >> removal of endpoints at runtime. I was contemplating using a ContextHandler >> or ServletContextHandler but from past experience I remembered that I could >> only add new contexts/servlets to Jetty and not remove them. Is this >> correct? >> >> > you should be able to do this at runtime providing you have a reference to > the server object, sort of implementation dependent so need to take a look > at your impl... > > actually I suspect we could tie into the deployment management for this and > make either a custom Configuration that looks for metadata describing this > stuff or an actual Provider that scans for a descriptor in a directory, > etc...or add as an option on the context's that the context provider scans > and deploys > > cheers, > jesse >