I like the idea. From a pure marketing perspective, TomEE Enterprise could be a possible alternative instead of TomEE Plus.
On Thu, Aug 18, 2011 at 6:09 PM, David Blevins <[email protected]> wrote: > > On Aug 18, 2011, at 3:06 PM, David Blevins wrote: > >> So with the Java EE 6 certification work we're doing we have some decisions >> to make. >> >> Currently, we're beyond plain Web Profile. The additional bits that we >> include are: >> >> - Connector >> - EJB Full (MDBs, CMP, etc) >> - JMS >> - JAX-WS >> - JAX-RS >> - JavaMail ? (not sure on that one) >> >> For the most part this means CXF and ActiveMQ. Two thoughts here: >> >> 1. It would be nice to be certified by JavaOne -- we might be able to make >> it if we scale back to the minimum >> 2. Some people might prefer something that doesn't contain ActiveMQ & CXF >> anyway >> >> So i'm wondering if we shouldn't take what we currently call TomEE and split >> it into two distros: >> >> - TomEE >> - TomEE Plus >> >> The first would be the bare minimum for a web profile impl. This is the one >> we could probably certify by JavaOne. The second would be what we think of >> as TomEE now, i.e. it has extra bits we think are useful in the real world. >> We can still certify this, but will take a bit longer -- my guess is a >> couple months. >> >> I'm guessing for the plain TomEE distro we could cut the libs down to half. >> Aside from ActiveMQ & CXF and their dependencies being trimmed, we could cut >> out Quartz (EJB Full @Schedule support) and likely a few other things. >> >> In general it seems like a good idea to give people the choice. People >> could do a bit more "build your own stack" on top of the slimmed TomEE >> distro than with the fuller TomEE distro. >> >> >> Thoughts? > > Note on the marketing side. We would get to make two certification > announcements which is pretty cool :) > > > -David > > -- Karan Singh Malhi twitter.com/KaranSinghMalhi
