You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by David Blevins <da...@gmail.com> on 2011/08/19 00:06:50 UTC
TomEE Plus?
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?
-David
Re: TomEE Plus?
Posted by David Blevins <da...@gmail.com>.
If we can boot and run without CXF, that's good enough. I know the core can, not sure on TomEE itself.
With our deployment design the way it is (split between config and assembly) we can do all sorts of things to the app prior to handing it over to the Assembler. There's already some code that can strip out JMS & CMP (DebuggableVmHackery) and some that can strip out Web Services and references to Web Services (RemoveWebServices).
So we can strip things out and issue a warning, deploying the "trimmed" app. Or we can reject the app and issue failures. Can easily do both and make it configurable via a flag.
-David
On Aug 18, 2011, at 9:49 PM, Romain Manni-Bucau wrote:
> today WS, RS are pretty integrated and not in a very pluggable way in core
> etc so if you find there is an easy way to split tomee it is a good idea
> otherwise it is probably a bad idea, we'll have a more complicated code to
> gain nothing special excepted some Mo.
>
> - Romain
>
> 2011/8/19 David Blevins <da...@gmail.com>
>
>>
>> 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
>>
>>
Re: TomEE Plus?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
today WS, RS are pretty integrated and not in a very pluggable way in core
etc so if you find there is an easy way to split tomee it is a good idea
otherwise it is probably a bad idea, we'll have a more complicated code to
gain nothing special excepted some Mo.
- Romain
2011/8/19 David Blevins <da...@gmail.com>
>
> 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
>
>
Re: TomEE Plus?
Posted by dsh <da...@googlemail.com>.
No it sounds like a solution for enterprises ;)
On Tue, Sep 6, 2011 at 4:08 PM, Romain Manni-Bucau
<rm...@gmail.com> wrote:
> TomEE enterprise sounds too much like a commercial solution, isn't it?
>
> - Romain
>
> 2011/9/6 Karan Malhi <ka...@gmail.com>
>
>> 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 <da...@gmail.com>
>> 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
>>
>
Re: TomEE Plus?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
TomEE enterprise sounds too much like a commercial solution, isn't it?
- Romain
2011/9/6 Karan Malhi <ka...@gmail.com>
> 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 <da...@gmail.com>
> 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
>
Re: TomEE Plus?
Posted by Karan Malhi <ka...@gmail.com>.
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 <da...@gmail.com> 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
Re: TomEE Plus?
Posted by David Blevins <da...@gmail.com>.
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