Re: Java EE on tomcat?
On 9/8/2011 3:08 PM, nroberts wrote:
On Sep 8, 11:22 am, Lew<lewbl...@gmail.com> wrote:
That said, most systems run better on Tomcat, or better yet on
Apache Web Server + Tomcat, anyway. EJBs are a pain in the butt
most of the time, and queues have specialized use cases you might
not even have. For the stuff you most likely care about, namely
web pages, Expression Language (EL) the Java Persistence API (JPA),
and JSF/XHTML, Tomcat is eminently suitable.
I'm completely new to Java but in reading tutorials and such I'd
imagine writing Java web applications without EJB, especially the
current standard, would just add a bunch of work.
If the app you will be developing does not require any of the stuff
you are missing, then it will not have any impact at all.
That is not an unlikely scenario.
What could those concerns be? The program I'll be writing is
basically this thing that imports data into a database, does some
manipulations and comparisons, and outputs a "report" in a particular
command language. Various aspects of its use need to be limited by
access, pay-grade, responsibility...etc... Based on my limited
understanding, what exists now doesn't need to be THAT secure, but
what they may want to do later would need a great deal of security.
Is it reasonable to write such a thing with the parts of EE possible
to use with tomcat?
Yes.
Whichever way you go, push for the latest stable version of the app
server or Tomcat, and for Java 6 or 7 as the base language. Push hard.
There's no valid reason to go with Java 5 or J2EE in the platform, given
backward compatibility and the absence of license fees. Only development
and maintenance costs should weigh into that decision, and use of
outdated and obsolete tools affects those rather severely.
One thing I've pushed on is trying to upgrade our JBOSS server to the
current version (we're currently stuck on 4.0). I don't really know
what's going to be required to do this, how much work, etc...but I
felt it worth looking into. Just got a push-back hard, from multiple
directions, saying that we're rewriting the whole thing to only use
tomcat anyway.
It seems as if it has already been evaluated and a decision has
been made.
Arne