Community
Participate
Working Groups
Created attachment 180249 [details] WTP Adaptor for Jetty 7.x/Jetty 8.x + Docs This zip contains Plug-In for "WTP Adaptor for Jetty 7.x/Jetty 8.x" + "Jetty WebSocket Wizard" (only WebSocket servlet generation, not he HTML client). This WTP Adaptor is not a Generic Server. It looks like WTP Tomcat Adaptor. It's important to know that : * Code is very very very ugly because * I have developped that in 3 weeks. * I have copy/paste a lot of code coming from WTP Tomcat Adaptor. * I didn't know Jetty when I have started the Plug-Ins development. You will find in this patch /docs folder which contains ODT which is a Jetty WTP Adaptor+WebSocket Wizard documentation which show you screenshot which show you features of the WTP Adaptor for Jetty 7.x/Jetty 8.x like : * download the Jetty server * modify the port with UI. * modify the context path with UI. * use external WEB Application. * Generate WebSocketServlet with wizard. I have tried to explain a litlle how the Plug-In works with Jetty, but don't hesitate to tell me if some sections are not very good explained.
Perfect, thanks Angelo! Now to begin the discussion of where to put it...Does anyone know some WTP people we can get onto this issue to discuss where the continuing development of this plugin ought to occur? I am fine with opening a CQ and getting it into jetty itself but it seems like perhaps WTP might be the best location for it. Or perhaps it should come to Jetty initially and then target being moved to WTP at a later point? Interested in others thoughts on the matter! cheers, jesse
(In reply to comment #1) > Perfect, thanks Angelo! > > Now to begin the discussion of where to put it...Does anyone know some WTP > people we can get onto this issue to discuss where the continuing development > of this plugin ought to occur? > > I am fine with opening a CQ and getting it into jetty itself but it seems like > perhaps WTP might be the best location for it. Or perhaps it should come to > Jetty initially and then target being moved to WTP at a later point? > > Interested in others thoughts on the matter! > > cheers, > jesse I think Keith Chong or Valentine Baccui would be good starting points. As well as David Williams should be involved if you are looking for WTP to be the eventual home.
In terms of build process having it with WTP is the one solution that makes sense as all its dependencies are related to WTP. If we were to build it ourselves we would have to use a separate build that takes place after WTP is built.
We talked about this on the RT-PMC call today and the general thinking was that it ought to live in the jetty svn area so we have our committers able to work on it directly and then we need to open up the discussion on how and where it gets included into a release when the time comes that we are happy with the stability of it, etc. Hugues, do you think this could easily be added into the tycho setup we already have in place or should this be a new area in svn entirely? In the meantime I'll start up the CQ process on getting it ok'd to commit to svn.
As far as the build tool is concerned it is not difficult to add it to the current eclipse folder with the tycho build. There are 2 benefits to making a separate build for this though: 1- Build schedule: the WTP adaptor depends on WTP which would make jetty a +3 build. Currently Jetty is a +1 build. 2- The WTP adaptor will be packaged as a feature. That is a simpler build than the RTStarterKits that are products by themselves. As a consequence we can use the mainstream version of tycho to build the WTP adaptor. I would favor a separate folder.
Date: 2010-10-26 16:47:54 -0400 (Tue, 26 Oct 2010) New Revision: 2407 thanks Angelo!
