My point was more towards the issue of Tomcat not being an EJB container and the apparent scope of the company would make EJBs mandatory for handling data access.
But I know what you mean about a company getting cheap on you. I am forced to used JRun (chosen solely based on the price), arguablly the worst app server on the planet. And stop sending that Foster's crap up here - we want real beer! Cheers! Mark -----Original Message----- From: Dan Washusen [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 17, 2002 10:50 PM To: Struts Users Mailing List Subject: RE: Things that use Struts Like I said, it's only a proof of concept. The company in question is used to paying a LOT of money for it's application servers, apparently they almost jumped at the chance at cutting that cost to near nothing... I'm only a lowly dev on the project and don't really know any of the politics associated. At the moment the only technical issues I am aware of with tomcat is it's comparably ineffective method of session management and fail over (being restricted to one apache instance for the tomcat sticky sessions). Anyway, I just thought you might like to know about it. We are definitely using Struts, Tomcat may change due to the above issue. -----Original Message----- From: Mark Galbreath [mailto:[EMAIL PROTECTED]] Sent: Friday, 18 January 2002 12:23 PM To: Struts Users Mailing List Subject: Re: Things that use Struts "One of Australias' biggest sites?" How are you going to that with Tomcat? Cheers! Mark ----- Original Message ----- From: "Dan Washusen" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Thursday, January 17, 2002 8:02 PM Subject: RE: Things that use Struts > Hey everyone, > I'm currently working on a proof of concept for a re-write of one of > Australia's biggest sites (just under a million searches a month). The > proof of concept runs the front end (presentation layer) on Linux with > Tomcat 4 and Struts. I'll keep you posted on how it goes (so far so good). > There is even some talk of Lucene being used. > > Needless to say, we are very impressed with both Tomcat and Struts. > > Cheers, > Dan > > -----Original Message----- > From: Stuart Charlton [mailto:[EMAIL PROTECTED]] > Sent: Friday, 18 January 2002 10:01 AM > To: '[EMAIL PROTECTED]' > Subject: Things that use Struts > > > Hi everyone, > > I've been a Struts developer and lurker since 1.0 was first released and > have been pushing it in a big way within my company... Just wanted to throw > in my two cents about where we're using Struts for people who are wondering > whether Struts is right for their project, or if it can tackle a large scale > system. > > a) We have a subcontract that's replacing a system for a division of the > U.S. Navy. This system is replacing 1.5 million lines of COBOL code with a > J2EE solution using Struts, WebLogic and TOPLink. After 3 months of > development is nearly 60,000 lines of code and will be around 150,000 by the > time we're done. Most of the screens are pretty static, but this is > definitely a huge system, and Struts' design paradigm has scaled gracefully > (with a lot of help from TOPLink). > > b) One of our financial clients is using a web-based inventory system for > trading whole loans & mortgages. This will be refactored to incorporate > Struts over the next several months (currently it's a bit icky, somewhere > between JSP model 0 or 1 in terms of modularity). > > c) Our new venture with Random House, http://www.codenotes.com/ was written > completely with Struts on JRun. > > Struts is a great framework, the code is clean enough to eat off of, and it > really makes J2EE sing. With a lot of the new whiz-bang ASP.NET features > coming down the pipe, I think Struts really is what's keeping JSP/Servlet > development competitive.... > > Cheers > Stu Charlton > Senior Architect / Trainer, Infusion Development > Disclaimer: Everything in this message is the opinion of your humble > correspondent and is not necessarily the opinion of Infusion Development > corp. > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
