Maybe the existing OpenEJB adapter could be simply extended to support both OpenEJB standalone and TomEE. Or the existing OpenEJB WTP adapter and the existing Tomcat adapter could be merged into a new TomEE adapter which would make it almost transparent to the user whether a standalone OpenEJB, TomEE or TomEE plus is being used (depending on the server runtime used the WTP editor page could provide different tunables). I suspect the original OpenEJB WTP adapter could have been a copy of the generic or Tomcat WTP adapter to so it would maybe a good idea anyway to have a look at it to figure out whether WTP APIs used are still up-to-date or not.
Cheers Daniel On Mon, Apr 30, 2012 at 6:47 PM, Jonathan Gallimore <[email protected]> wrote: > There isn't a TomEE Eclipse plugin, but there is an OpenEJB one, which > includes a WTP server for OpenEJB, and a wizard to migrate from EJB2.1 to > EJB3, generating the relevant annotations. I'm no expert but I do have some > experience of doing Eclipse plugins, and did a fair amount of work on the > OpenEJB one. > > I'd love to get back into some of that stuff. The big question is, how > should a TomEE plugin work, and how would it be different from a Tomcat > one? I've always found the Tomcat one works really well for TomEE - I've > presented this a couple of times at JAX London, and one of the things > people liked was that the existing Tomcat tools worked with TomEE. > > I'm quite happy to try and see if we can come up with a TomEE adaptor based > on the Tomcat plugin and make it a bit easier to get TomEE going (there > were a couple of options you have to fiddle with on the Tomcat WTP plugin) > - are there any other ideas that people have? > > Jon > > On Mon, Apr 30, 2012 at 5:25 PM, Neale Rudd <[email protected]> wrote: > >> Is there an Eclipse plugin for TomEE yet? >> >> Does anyone have experience with building Eclipse plugins? >> >> I personally don't use Eclipse either but a lot of our customers do. >> >> Now that TomEE is officially released, it would be great to have that as >> an option in the main eclipse build, especially since other distros like >> Glassfish have one. It's probably exactly the same as the Tomcat one - but >> adding it as an explicit option would boost recognition. >> >> Best Regards, >> Neale >> >> >> >> ----- Original Message ----- From: "dsh" <[email protected]**> >> To: <[email protected]> >> Sent: Tuesday, May 01, 2012 1:42 AM >> Subject: Re: Getting Started video >> >> >> >> On Mon, Apr 30, 2012 at 2:51 PM, David Blevins <[email protected]> >> wrote: >> >>> >>> Seems like a lot of these suggestions involve having TomEE support >>> already in the Eclipse binary that people download from eclipse.org. >>> That sounds great. Do you know how to do that? >>> >>> >> In the first place a downloadable plug-in containing the WTP adapter >> for TomEE would be enough. A second step would be pushing the whole >> thing upstreams to the Eclipse project like it is the case for Tomcat >> or WAS CE. I could have a look at that. >> >> If I misunderstand it's because I don't really like Eclipse and I don't >>> know what I'm doing :) >>> >>> >> I'd say in that particular case you are more like a generalist who >> just knows enought to operate any IDE :) >> >> >>> Console messages we can control. Stop button out of our control unless we >>> write a TomEE adapter. >>> >>> >> I noticed that Tomcat, for whatever reason prints out info and warning >> messages to stderr instead of stdout too. Now idea why. Thus the red >> instead of normal, black messages. >> >> Btw, which screencasting program did you use to do the webcast recording? >> >> Cheers >> Daniel >>
