I use OJB accessing the database with PB API. I use a nested bean approach that allows me to easily write transactions to a datbase. I have a design pattern that is quite simple and light-weight. It has provided a way to "truly" divide the view and controller from the model/logic. Struts plays the role of transporting beans around and checking some web tier specific stuff. The rest is handled by my biz logic and OJB. It even allows for DB independence if that matters to you.
Brandon Goodin Phase Web and Multimedia P(406)862-2245 F(406)862-0354 http://www.phase.ws -----Original Message----- From: Joe Barefoot [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 03, 2002 1:49 PM To: Struts Users Mailing List Subject: RE: Should I use a persistence layer? Our shop uses Castor, which is good for getting you up and running quickly as it can generate entity object code from a database schema. I don't know about simplicity, however...I don't think any persistence layer is really that simple. :( peace, Joe > -----Original Message----- > From: Chen, Dean (Zhun) [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 03, 2002 12:25 PM > To: 'Struts Users Mailing List' > Subject: RE: Should I use a persistence layer? > > > Thanks for this, what good persistence layers are there? Is > there something > that works with struts and is simple? > > Dean Chen > > > > > -----Original Message----- > From: Joe Barefoot [mailto:[EMAIL PROTECTED]] > Sent: Thursday, October 03, 2002 2:41 PM > To: Struts Users Mailing List > Subject: RE: Should I use a persistence layer? > > > Yes. The standard approach is to only keep in memory results that are > currently on the page. Have a persistence layer (either EJB > or O/R mapping > tool, or a combination of the two) "page" the results for > you. i.e., you > give it search criteria, sort criteria, a begin index, and an > end index, and > it gives you back the results. This solves two problems: > The one you are > encountering with bad results with two different windows, and > the memory > problems associated with very large result sets. > > There are examples of this sort of implementation out there; > sorry I can't > provide links. :( > > peace, > Joe > > > -----Original Message----- > > From: Chen, Dean (Zhun) [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, October 03, 2002 10:13 AM > > To: 'Struts Users Mailing List' > > Subject: Should I use a persistence layer? > > > > > > Hi, > > > > For an web application, is there a way for a user to > paginate through > > (similar to google) a lot of data across multiple browser windows. > > > > The usual way of paginating with session scope works fine. > > However, if a > > user has 2 windows open on the same application. When he/she > > queries on one, > > then queries on another, and then comes back to the first > > window and click > > "Next", he/she will get bad results. > > > > Does this lead to EJB or any other persistence layers? > > > > Thanks, > > > > > > Dean Chen > > > > > > -- > > 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]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
