struts-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ajay Chitre <ajay.chi...@diligentteam.com>
Subject Re: Struts & Tomcat 4.0
Date Fri, 10 Aug 2001 07:08:41 GMT
Thank you everybody for sparing time to answer my questions.  It is support
like this that makes me want to use all the Jakarta products more and more.

Thanks (a lot) again!

- Ajay


-- Original Message --

>Keeping in mind that my "day job" is building Tomcat 4, I will add a few
>comments and answers below.
>
>On Wed, 8 Aug 2001, Ajay Chitre wrote:
>
>> Hello,
>> 
>> I have been "playing" with struts for the past couple of months and I
have
>> had fun playing with it.  Time has come now to stop playing and get serious.
>> 
>> I have been asked to develop a web app with Struts & Tomcat.  I have
been
>> using Weblogic for the past couple of years, but this is my first experience
>> with Tomcat, so I need some help to take some decisions.  (I realize
that
>> this email should really be sent to the Tomcat mailing list, but I believe
>> there's enough expertise in this mailing list to get these questions
>> answered!)
>> 
>> After reading thru the Struts mailing list I have concluded the following.
>> Can someone please tell me if I am on the right track?
>> 
>> 1)  From one of Craig's emails it sounds like I should be using Tomcat
>4.0,
>> not 3.2.  Is that right?  But Tomcat 4.0 is a beta release.  Is it reliable?
>> 
>
>Tomcat 4 is beta only because the specs are not yet final -- that is a
>short term issue (all the J2EE specs will be going final together
>soon).  The code itself is very solid for stand-alone use, which is the
>typical mode for application developers.  The web connector code is less
>mature, but getting there fast.
>
>I use Struts + Tomcat 4 every day -- it's part of my unit test procedures
>on Tomcat 4 development that it *must* run Struts apps flawlessly :-).
>
>Note also that, while Tomcat 4 supports the new Servlet 2.3 and JSP 1.2
>specs, it also runs Servlet 2.2 / JSP 1.1 based applications (which is
the
>minimum platform for Struts) just fine.  Backwards compatibility like this
>is a requirement in the 2.3/1.2 specs.
>
>> 2)  Doesn't look like Tomcat 4.0 supports EJB.  Does it?
>> 
>
>No, and it won't.  For developing web apps that use EJBs, you can use
>something like the J2EE RI (version 1.3 includes Tomcat 4 as it's web
>layer), JBoss (which integrates with Tomcat, although still 3.2 IIRC),
or
>other similar environments.
>
>> 3)  If EJB is not available I can use JDBC - no problem - but doesn't
look
>> like I can create database connection pool in Tomcat.
>> 
>
>You've got three different ways to do connection pools in Tomcat 4:
>
>* As application-provided resources (i.e. the <data-source> declaration
>  in "struts-config.xml", using the connection pool already
>  included in Struts.  This works in Tomcat 4 just like it works in
>  any other servlet container.
>
>* Using a third party connection pool implementation like Poolman
>  (again just like any servlet container).
>
>* As JNDI-accessed resources (exactly as in the J2EE programming model).
>  This is a little tricky to set up (due entirely to sketchy
>  documentation) but is very useful when you plan to deploy on a J2EE
>  environment (because they all support this feature).
>
>> 4)  From one of Ted's emails I think I should use Poolman to create database
>> connection pool in Tomcat 4.0.  Right?
>> 
>
>That's one option.  Or you can use the one built in to Struts.  Or you
can
>use the JNDI-based support built in to Tomcat 4.
>
>> 5)  What's equivalent of Weblogic Time APIs?  Tomcat workers, right?
>> 
>
>I assume this is for background job scheduling and stuff?  You can deal
>with this in a variety of ways:
>
>* Add some code to Tomcat's internals (there are appropriate APIs
>  and listeners to do this kind of thing)
>
>* Add a servlet-based job scheduler and run it as a web app (something
>  like this is much more likely to be portable to other servers too).
>
>Nothing is provided for this out-of-the-box.
>
>> 6)  Can I set up Tomcat to send emails using Java Mail APIs?  In Weblogic
>> one has to make sure that mail.jar & activation.jar is in Weblogic
>> Classpath.  Is there any special requirement such as this in Tomcat?
>> 
>
>The only requirement is that you make the necessary JARs available.  In
>Tomcat there are (again) two options:
>
>* Include activation.jar and mail.jar in /WEB-INF/lib of your
>  application (portable to *any* container)
>
>* Include these JAR files in $CATALINA_HOME/lib, which makes them
>  available to all web applications.
>
>> 7)  Does Tomcat support JMS?
>> 
>
>You can certainly write web apps that use the JMS client APIs, in the same
>way that you can write mail clients that use JavaMail APIs.  Tomcat is
not
>a JMS server -- again, that is a J2EE app server level feature.
>
>> 8)  Which one is better - Log4J or LogKit (which is part of Avalon project
>> from Jakarta)?
>> 
>
>I'm not going to touch that one :-).
>
>> 9)  What's the difference between 'Struts' & 'Turbine' (which is another
>> Jakarta project)?  Pros & Cons?
>> 
>
>Ted's pointer gives a pretty good summary.  There's also a fairly even
>handed comparison on the Barracuda site at Lutris.
>
>That being said, people who like JSP, and J2EE-ish APIs, will tend to
>prefer Struts, while those who like Velocity/WebMacro, and don't
>necessarliy care about J2EE-ish APIs, will tend to like Turbine.
>
>> I apologize for the length of this email.  Thanks in advance for your
time.
>> 
>> - Ajay
>> 
>> 
>
>Craig
>
>
>

Ajay Chitre

Diligent Team, Inc.
(Where Diligent People Work as a Team)

http://www.DiligentTeam.com



Mime
View raw message