Re: [jetty-user] Jetty JAX-WS 2.2 SPI implementation?

First step would be to create an issue on bugs.eclipse.org under RT/Jetty
and attach this source.  Make the subject of the bug something appropriate
like 'Contribution: foo'  Then I can start the process with Sharon to get it
reviewed for IP and whatnot.

I'll talk with greg a bit on what we should name the other module so we can
integrate this into the existing http-spi module once that is homed at
eclipse.  Then I'll take a patch from you in the form mentioned here:
http://wiki.eclipse.org/Jetty/Contributor/Contributing_Patches

Then you will have your name in lights in the eclipse git repo and start
building your karma with jetty :)

Really, its just opening that issue and making a statement like 'I wrote
100% of this code and make no IP claims on it, yadda yadda yadda'

cheers,
jesse

--
jesse mcconnell
[email protected]

http://webtide.com / http://intalio.com
(the folks behind jetty and cometd)


On Thu, Sep 29, 2011 at 17:39, Aaron Anderson <[email protected]> wrote:

> Hi Jesse,
>
> Yes I am. How can I assist?
>
> Regards,
>
> Aaron
>
> ------------------------------
> *From:* Jesse McConnell <[email protected]>
> *To:* [email protected]
> *Sent:* Thursday, September 29, 2011 2:46 PM
>
> *Subject:* Re: [jetty-user] Jetty JAX-WS 2.2 SPI implementation?
>
> Shocking...we have approval to move the existing http spi interface over to
> jetty at eclipse now...So Aaron, are you still interested in contributing
> this?
>
> cheers,
> jesse
>
> --
> jesse mcconnell
> [email protected]
>
>
> On Fri, Jul 15, 2011 at 09:47, Jesse McConnell <[email protected]>wrote:
>
> Hi Aaron,
>
> I haven't forgotten you...annoying process time.  I need you to open a bug
> @ bugs.eclipse.org for rt.jetty with this attached as a contribution.
>  Then I can start the legal process to get it pulled into the project at
> large.  I am working to get the http-spi module over to eclipse as well and
> we might as well glom it all together there once it is all said and done.
>
> once I start the process then someone from eclipse will contact you about
> the code and ideally we'll be good shape.
>
> ultimately, once it is in jetty eclipse git, since we are being mirrored at
> github we can work with you through that to take in patches and changes
> moving forward with it.
>
> cheers,
> jesse
>
> --
> jesse mcconnell
> [email protected]
>
>
> On Tue, Jul 5, 2011 at 11:21, Aaron Anderson <[email protected]>wrote:
>
> Great, just let me know on how I can assist.
>
> Aaron
>
>
> --- On *Fri, 7/1/11, Jesse McConnell <[email protected]>* wrote:
>
>
> From: Jesse McConnell <[email protected]>
> Subject: Re: [jetty-user] Jetty JAX-WS 2.2 SPI implementation?
> To: [email protected]
> Date: Friday, July 1, 2011, 5:28 PM
>
>
> 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] <http://mc/[email protected]>
>
>
> On Fri, Jul 1, 2011 at 07:51, Jesse McConnell <[email protected]<http://mc/[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
>
>
>
>
>
>
>