RE: Tomcat + Struts in Production Environment

You don't have to use EJBs just to take advantage of an app server's connection pooling. I think the advantage of using EJB is that the App Server has connection pooling. And AppServers supports caches (??) -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail:

RE: Tomcat + Struts in Production Environment

plus: there are connction pools and caches that can be integrated into servlet-engines... -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Monday, December 10, 2001 4:11 PM To: [EMAIL PROTECTED] Subject: RE: Tomcat + Struts in Production Environment You

Re: Tomcat + Struts in Production Environment

and template tags since they are most useful. You can get away without bean and logic in many cases. Sean - Original Message - From: L. Yeung [EMAIL PROTECTED] To: Struts Users Mailing List [EMAIL PROTECTED] Sent: Saturday, December 08, 2001 10:55 AM Subject: Tomcat + Struts in Production

Re: Tomcat + Struts in Production Environment

--- Vic Cekvenich [EMAIL PROTECTED] wrote: Hi All! Just a little intro about my work and myself. I'm the only employee of a startup software company writing database solutions. I'm told to write an application for POS, invoicing and inventory modules that should scale for around

Tomcat + Struts in Production Environment

Hi All! Just a little intro about my work and myself. I'm the only employee of a startup software company writing database solutions. I'm told to write an application for POS, invoicing and inventory modules that should scale for around less than 30k but greater than 10k transactions per day.

Re: Tomcat + Struts in Production Environment

Hi All! Just a little intro about my work and myself. I'm the only employee of a startup software company writing database solutions. I'm told to write an application for POS, invoicing and inventory modules that should scale for around less than 30k but greater than 10k transactions per