And here is the reply which (again) should clarify all those questions:

Meecrowave is _not_ duplicating TomEE. TomEE is based on the app assembler 
which is in turn heavily based on OpenEJB and all the other integrated 
technologies like JMS, etc.Meecrowave has been there as tomcat boot module 
almost ever since OWB existed. It's kind of the totally inverse approach. It is 
tomcat + CDI centric and uses CDI to integrate all the other technologies as 


    On Thursday, 22 February 2018, 07:43:55 CET, Gurkan Erdogdu 
<> wrote:  
  Hi allSeveral months ago I advised to create another profile under TomEE (or 
create another TLP project) instead of duplicating the work in Meecrowave 
project but Romain and Mark rejected. Now, come to the same point :) There are 
lots of separate projects (or subprojects, or modules) in Apache (Geronimo, 
TomEE, Meecrowave. I think all of these modules must belong to TomEE. Lots of 
users are confused with this


    On Thursday, February 22, 2018, 12:41:19 AM GMT+3, Romain Manni-Bucau 
<> wrote:  
 Le 21 févr. 2018 22:33, "Bruno Baptista" <> a écrit :

Hi All,
Is it a given that in the future we will use on TomEE both:

Can we assume that from now on?

In the MP distro probably yes. Stack (dependencies) will pby be refined for
safeguard since current one is not that friendly for tomee IMHO - tomcat
classloading part + size - but not yet a blocker. Config is good for a


Bruno Baptista

On 21-02-2018 18:49, Roberto Cortez wrote:

> Hi guys,
> I've been looking a little bit in how to use some of the existent Apache
> MP implementations with TomEE and here are some ideas / conclusions.
> MicroProfile Configuration:Using
> Just adding the jar, plus API to TomEE libs seems to be enough.
> MicroProfile Fault Tolerance:Using https://github
> .com/apache/geronimo-safeguard. Added the jars and the API to TomEE libs
> and also required to set TomEE configuration 
> tomee.webapp.classloader.enrichment.prefixes
> to safeguard-impl. This is to add the required CDI Beans that are part of
> safeguards into the webapp context. With this, it seems to work just fine.
> If this would be part of the dist, I guess we would need to add the
> required CDI Beans into org.apache.openejb.cdi.CdiScanner.
> MicroProfile Rest Client:Apache CXF added a MP Rest Client module. The
> issue is that it is added into the 3.2.x line, which is JAX-RS 2.1. If we
> look into the MP spec, the Rest Client should be compatible with JAX-RS
> 2.0, which is implemented in CFX 3.1.x line. Upgrading TomEE to CFX 3.2.x
> doesn't really work due to the JAX-RS 2.1 dependency. As a workaround, I've
> also tried to use just the CFX 3.2.x module lib MP Rest Client, but there
> is some dependent code. Made a few local changed and got it to work, but
> ideally, the MP Rest client should be ported back to CFX 3.1.x to support
> MP 1.3.
> Couldn't find any other Apache implementations for the other MP specs.
> I've also think that it could be interesting to distribute a TomEE flavour
> with just the MP stuff, to slim down the binary.
> Any thoughts?
> Cheers,Roberto

Reply via email to