> -----Original Message----- > From: Robert J. Sanford, Jr. [mailto:[EMAIL PROTECTED]] > Sent: Friday, October 04, 2002 3:00 PM > To: Struts Users Mailing List > Subject: RE: Persistence Framework Comparison? > > > There are two things that I want/need in a persistence > framework and I have > yet to find them. I know that OJB does not support them and I have not > looked very hard at the others. Maybe you can tell me if your product > handles them. > > 1) Read only attributes so that a setter method is not automatically > generated for one and that value is never persisted, just read.
So delete the setter(s) you don't want from your entity objects. Or just make them empty methods that don't actually do anything. > > 2) The ability to persist an object to a different "table" > than it was read > from. Yes this seems odd so let me explain in a few simple > words followed by > a simplistic example. The simple words are - performance and > simplicity. > When developing a web app database I tend to go for normalization. The > employees are in one table with a FK to the department table. > But, when > displaying the data on a page I want to display the name of > the department, > not its database ID. So, I use a view that joins the two > tables meaning that > a) I get all the data that I need in a single query I can > get all of the information I need for display (performance) > and... > b) I don't have to worry about reading data from multiple > queries and/or multiple objects (simplicity). > > But, I cannot guarantee that the view I am reading from is > updateable so I How can you not guarantee this if you are creating the data model? I don't understand. > have to insert/update to the simple tables (employee for instance). > > So, can you help me out here? Can your product do this? > > rjsjr > > > -----Original Message----- > > From: Robert [mailto:[EMAIL PROTECTED]] > > Sent: Friday, October 04, 2002 4:12 PM > > To: 'Struts Users Mailing List' > > Subject: RE: Persistence Framework Comparison? > > > > > > We have just released a free download for our eQ! software which you > > might want to take a look at: www.browsersoft.com/eQ > > > > The demo app is built using Struts for the controller, JSTL > for taglibs, > > our persistence layer and our XML scripting engine for > process logic. > > > > I'm the contact for it if you want more info. > > > > - Robert McIntosh > > [EMAIL PROTECTED] > > > > -----Original Message----- > > From: Karr, David [mailto:[EMAIL PROTECTED]] > > Sent: Friday, October 04, 2002 3:18 PM > > To: 'Struts Users Mailing List' > > Subject: RE: Persistence Framework Comparison? > > > > > -----Original Message----- > > > From: James Higginbotham [mailto:[EMAIL PROTECTED]] > > > Sent: Friday, October 04, 2002 1:12 PM > > > To: Struts Users Mailing List > > > Subject: RE: Persistence Framework Comparison? > > > > > > > > > > >(I wish Struts had a non implemented persistance interface) > > > > > > > > Really? I think Struts is quite good at what it does, > and to me, > > > > persistence seems to outside the scope of a web application MVC > > > > framework. > > > > > > Agreed. Struts does what it does best - web MVC > framework. What the > > > original author of the comments (sorry, lost in my mailbox > > > right now) is > > > looking for is what I would recommend happen on top of > > > Struts. Something > > > that takes Struts, a proven OSS O/R framework, and some > glue to make > > > DB-driven Struts applications faster to develop. > > > > > > Anything like that out there? Anyone working on this or have > > > one in the > > > planning stages? I've been wanting to craft one myself, but > > > haven't had > > > the time. But if one existed, I'd problem knock out a > couple of pet > > > projects faster. > > > > I haven't used it, but I get the feeling that the Expresso framework > > (http://www.jcorporate.com/) tries to fill this need to some extent. > > > > -- > > 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]>
