Try Torque and Fulcrum...they are part of the jarkata turbine project...now decoupled and you can use them independently of turbine.
Torque is a persistence layer framework Fulcrum is a collection of services such as security, upload, and etc... http://jakarta.apache.org/turbine/index.html -----Original Message----- From: Struts Newsgroup [mailto:[EMAIL PROTECTED]] Sent: Saturday, March 09, 2002 9:25 PM To: [EMAIL PROTECTED] Subject: Re: EBJ Alternatives? Subject: Re: EBJ Alternatives? From: Vic Cekvenich <[EMAIL PROTECTED]> === I do my own "custom" thing on top of Struts (and I think a few non-ejb people advocated custom solutions). I will be posting a "solution" on source forge as a Struts sample, I think this week. For presistance I use CachedRowSet. Since they are SQL commands, they are very scalable. For autorization I use container JAAS (table based) For most others, Struts would do. I also plan to expose my data/model layer as a Soap service for non - web applications. hth, Vic Gabriel Sidler wrote: > A couple weeks ago there has been an intense discussion on > this list about the use of EJB. Many people were quite > critical or at least cautious about EJB. I'd appreciate if > some of you could share what alternative component > architectures/frameworks you are using. > > I'm now starting on a new web project where distribution and > transactions, two of EJB's main feature, are no requirements. > The application is a web-based collaborative system with a > rather complex application logic but little database involvement. > There will be clients using HTML/HTTP and other using a SOAP- > like protocol. I am planning on using Struts for the Web-tier > and am looking for a component framework to implement the business > logic/data tier. If feel that EJBs wouldn't be the right technology > for this but am wondering what alternatives are. The things I > would like to see in such a component framework are: > - component life cycle support > - support for component relationships > - component naming and lookup > - authorization mechanism > - web request dispatching > - subscription/notification service > - logging > - configuration > - persistence > - some modularization concept > - some error handling concept > > How are you implementing this? Any framework you can recommend? > Thanks for sharing! > > Gabe > > > > -- > Gabriel Sidler > Software Engineer, Eivycom GmbH, Zurich, Switzerland > > > -- > 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]>
