check maven plugin and arquillian integration of other servers, they aren't that far so it is clearly differentials. Several tests I wrote wouldn't have been possible without tomee.
Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-05-23 10:49 GMT+02:00 Hildeberto Mendonça <[email protected]>: > Thanks for the input guys. Is it ok if I hack those features a little bit > and try to document them? > > I would like to concentrate on features that move TomEE steps ahead of > standards. Things that sound like a good idea, run like a charm, and don't > wait two years for a new standard iteration. I could identify the following > points that differentiate TomEE so far: > > - abstract ejbs > - interface ejb > - dynamic persistence unit > - embeddable ejb > - jca > > Points that I can see elsewhere, thus not differentials: > > - maven plugin > - arquillian integration > > Points that I'm not sure, thus I have to research/compare more: > > - memory foot print > - server events > - skinny war support > - simple customization > - custom resources support > - datasource pooling library pluggability > > Points out of scope: > > - apache based > - community > > Am I missing something else? > > > On Fri, May 23, 2014 at 7:04 AM, Romain Manni-Bucau > <[email protected]>wrote: > > > Hi > > > > I'd say support if abstrat ejbs, interface ejb (no impl), dynamic > > persistence unit (reloading), its maven plugin, its arquillian > integration, > > all the tests features, its community, it is apache based, the embeddable > > side of openejb, its server events, its skinny war support, its JCA > > features (JCA.next, deployment in wars...), its simple customization, its > > custom resources support, its datasource pooling library pluggability and > > surely more... > > Le 23 mai 2014 05:41, "Chamil Jeewantha" <[email protected]> a écrit : > > > > > Hi Hildererto, > > > > > > First thing is TomEE is a Java EE 6 Web Profile certified stack. > > > The architecture of TomEE is loosely coupled with Tomcat. > > > One can simply deploy TomEE war on a Tomcat and thats it for J2EE > > > environment. > > > TomEE's memory foot print is low. Its comparatively lightweight to most > > of > > > the other J2EE servers. Hence it can serve better with less resources. > > > > > > The above list is the only things I get into my mind (I am new too). > May > > be > > > some expert will explain the missing part. > > > > > > > > > On Fri, May 23, 2014 at 2:53 AM, Hildeberto Mendonça < > [email protected] > > > >wrote: > > > > > > > Hello everyone! > > > > > > > > I'm new here and excited about discovering TomEE. I have used it some > > > > months ago for evaluation purposes and now I would like to resume my > > > > involvement. And I would like to start with a topic for discussion: > > what > > > > are the features that one can only find on TomEE? Thinking beyond the > > > > JavaEE specification and outside of the box, what are the > > differentials? > > > > > > > > Thanks and sorry for the vague question. > > > > > > > > -- > > > > Hildeberto Mendonça, Ph.D > > > > Blog: http://www.hildeberto.com > > > > Twitter: https://twitter.com/htmfilho > > > > > > > > > > > > PS: happy to see influential CEJUG members here :-) > > > > > > > > > > > > > > > > -- > > > [email protected] > > > > > > > > > -- > Hildeberto Mendonça, Ph.D > Blog: http://www.hildeberto.com > Twitter: https://twitter.com/htmfilho <http://www.cejug.org> >
