Best answer is it's business as usual with regards to the three other bundles 
we offer.  Would simply add a fourth choice.

The main goal would be to TCK test this setup and flush out any issues.  There 
are some annoyingly strict rules around packaging of anything that's to be 
labeled Java EE Certified.  Anything required for certification can't be added 
after the fact (must be in the binary) and must be enabled by default -- at 
least as far as the TCK can see.

We do play quite a bit with the word "enabled" -- we can actually auto-enable 
quite a few things and TomEE is capable of quite a bit of lazy loading.  If you 
clear out your tomee.xml so it contains nothing more than "<tomee/>", the 
server will still start and still deploy your apps.  You'll see several log 
entries that say "Auto-Created Foo", which is TomEE effectively filling out the 
tomee.xml based on the needs of your app.

This currently works for anything you can declare via tomee.xml: JMS, 
DataSources, Connectors, Containers, etc.  TomEE won't load the respective 
providers (ActiveMQ, Hsqldb, OpenJPA, etc) unless it had to add one of it's 
resources to make your app run.

JSF is an exception to the rule.  We have yet to find a way to conditionally 
enable JSF only based on the data in the app and still pass the TCK.  It's fine 
for 99% of the TCK, but that 1% prevents us from (by default at least) lazy 
loading JSF like we do most everything else.

There's probably a way to do it given enough tenacity and time.  The later one 
being the more difficult to acquire :)


-David

On Jan 24, 2014, at 4:48 PM, Abhijit Sarkar <[email protected]> wrote:

> One thing we might like to consider is that all servers are modular these 
> days, and for good; many modules are activated on demand or only available as 
> separate packages. Gone are the days of huge monolithic downloads which 
> started MQ services even if I were deploying a single JSP. Is the PLUME going 
> to be deviation from that?
> Regards,Abhijit
> 
>> From: [email protected]
>> Subject: Mojarra and EclipseLink bundle?
>> Date: Fri, 24 Jan 2014 16:39:38 -0800
>> To: [email protected]
>> 
>> I've checked in the start of a possible bundle we might want to consider 
>> offering, basically a version of TomEE Plus with Mojarra and EclipseLink.  
>> Tentatively called it "TomEE Plume" which stands for TomEE PLUs, Mojarra, 
>> Eclipselink (PLU.M.E).  Of course, should we want the bundle, whatever name 
>> is fine.
>> 
>> The idea is to provide people leaving GlassFish and shopping around for a 
>> replacement an easier on-ramp to TomEE.  With the announcement of the end of 
>> commercial support for GlassFish, there are more than a few of those 
>> floating around.
>> 
>> Thoughts?
>> 
>> 
>> -David
>> 
>                                         

Reply via email to