You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomee.apache.org by Romain Manni-Bucau <rm...@gmail.com> on 2012/10/24 00:33:15 UTC
why not tomee?
Hi guys,
just saw http://emmanuel-pavaux.blogspot.fr/2012_06_01_archive.html (ok it
is in french but will explain)
the guy explains at the end that not choosing an open source JEE6 server (i
let you guess which one ;)) and to pay for a server can be reasonable
because
1) the datasource pool config is better
2) remote ejb
3) rest
4) soap webservices
5) timer
...we have these stuff so maybe we don't speak enough about it in our
slides and we speak too much about fun and Web Profile
wdyt?
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
Re: why not tomee?
Posted by dsh <da...@gmail.com>.
Well I saw a somehow, IMHO biased comparison between WebSphere Liberty
Profile and Apache Tomcat. Both were positioned as app servers. I
asked why they don't compare app servers with app servers (i.e.
Liberty Profile with Apache TomEE) instead of app servers with servlet
containers. The answer was: customers ask for Apache Tomcat so we
compare with what customers are asking for. I as well thought that our
marketing may not address this. E.g. it should be common sense that
you should pick TomEE if you like to use an app server and not Tomcat.
Maybe it's just that way cause Tomcat has a history and TomEE doesn't
have one yet...
Cheers
Daniel
On Wed, Oct 24, 2012 at 12:33 AM, Romain Manni-Bucau
<rm...@gmail.com> wrote:
> Hi guys,
>
> just saw http://emmanuel-pavaux.blogspot.fr/2012_06_01_archive.html (ok it
> is in french but will explain)
>
> the guy explains at the end that not choosing an open source JEE6 server (i
> let you guess which one ;)) and to pay for a server can be reasonable
> because
> 1) the datasource pool config is better
> 2) remote ejb
> 3) rest
> 4) soap webservices
> 5) timer
>
> ...we have these stuff so maybe we don't speak enough about it in our
> slides and we speak too much about fun and Web Profile
>
> wdyt?
>
> *Romain Manni-Bucau*
> *Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
> *Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
> *LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
> *Github: https://github.com/rmannibucau*
Re: why not tomee?
Posted by Romain Manni-Bucau <rm...@gmail.com>.
Hi,
great you can enhance it,
about timer not sure, @Schedule i guess (was not explicitely said in the
blog post)
about tomcat config i think he spoke about tomcat-jdbc (which is now
supported)
*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*
2012/10/27 Jacek Laskowski <ja...@japila.pl>
> On Wed, Oct 24, 2012 at 1:33 AM, Romain Manni-Bucau
> <rm...@gmail.com> wrote:
>
> > 1) the datasource pool config is better
>
> I can support this opinion as I wish Tomcat's <Resources> should be
> supported which glancing at the code are not (the XML format is
> different from what Assembler expects).
>
> > 2) remote ejb
>
> I'll add a slide and demo for this, but given the time constraints (50
> minutes) it's nearly impossible to talk about TomEE+ in general and do
> demos afterwards. Tried it twice in a row - for JDD last Thursday and
> today on JavaDay in Kiev - and almost found time for the stuff I speak
> about now. Gotta be faster I believe, but it could be for less
> understanding of the audience.
>
> > 3) rest
> > 4) soap webservices
>
> Did these with the help of Dave's Awesome example. It's always fun to
> see people's faces when they see @WebService and @Path working in
> TomEE.
>
> > 5) timer
>
> Could you elaborate more on the feature and how you'd like to demo it?
> I appreciate and would show it in the other two conferences where I'm
> speaking about TomEE.
>
> I fully agree we should differentiate TomEE from the rest so we're
> uncomparable and perhaps unbeatable :)
>
> Jacek
>
> --
> Jacek Laskowski
> Functional languages (Clojure), Java EE, and IBM WebSphere -
> http://blog.japila.pl
> "Never discourage anyone who continually makes progress, no matter how
> slow." Plato
>
Re: why not tomee?
Posted by Jacek Laskowski <ja...@japila.pl>.
On Wed, Oct 24, 2012 at 1:33 AM, Romain Manni-Bucau
<rm...@gmail.com> wrote:
> 1) the datasource pool config is better
I can support this opinion as I wish Tomcat's <Resources> should be
supported which glancing at the code are not (the XML format is
different from what Assembler expects).
> 2) remote ejb
I'll add a slide and demo for this, but given the time constraints (50
minutes) it's nearly impossible to talk about TomEE+ in general and do
demos afterwards. Tried it twice in a row - for JDD last Thursday and
today on JavaDay in Kiev - and almost found time for the stuff I speak
about now. Gotta be faster I believe, but it could be for less
understanding of the audience.
> 3) rest
> 4) soap webservices
Did these with the help of Dave's Awesome example. It's always fun to
see people's faces when they see @WebService and @Path working in
TomEE.
> 5) timer
Could you elaborate more on the feature and how you'd like to demo it?
I appreciate and would show it in the other two conferences where I'm
speaking about TomEE.
I fully agree we should differentiate TomEE from the rest so we're
uncomparable and perhaps unbeatable :)
Jacek
--
Jacek Laskowski
Functional languages (Clojure), Java EE, and IBM WebSphere -
http://blog.japila.pl
"Never discourage anyone who continually makes progress, no matter how
slow." Plato