Hi Robert, Struts does not provide any type of support for data storage or retrieval, those details are left to the developer. In fact, discussion of such topics on this list often lead to pissing contests over EJB vs. RowSet.
I (personally) use OJB (http://jakarta.apache.org/OJB) not only for the benefit of O/R Mapping, but also connection pooling and caching. (Too many features to list here) For role-based navigation, you might try searching the archives, I’ve seen it mentioned a few times in the past. James Mitchell Software Engineer/Struts Evangelist http://www.open-tools.org > -----Original Message----- > From: Robert Hendley [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, October 15, 2002 11:28 PM > To: Struts Users Mailing List > Subject: Newbie Questions / Direction > > > I am a php developer mainly. And am in the learning curve for > JSP/Servlet development. I am sold on Stuts, I have read 20+ articles on > Struts and have found them helpful. My problem is information overload. > I am trying to port a php application to Struts that manages inventory > and invoicing. I am wondering if any one has written an application like > that using Struts. Or if one could give me some direction on where to > start. I have deployed several webapps with success and used a cookbook > approach to modify and tweak etc.. So if you have a moment I have a few > questions. > > > 1. How did you handle record locking ? As an example editing a customer > record and not allowing two to edit at the same time. > I am thinking a hash but where to put it? > > 2. I want to have a cache at the application scope of the "open" > invoices > , approx (100-200) about 1k each. The application currently uses 27 > tables, so any invoice can require up to 12 queries(I did not design the > schema)I have no real idea where to start with this. > > 3.What if any advice could you give for a navigation system that has > properties that are only available to a user/group? > > Thanks > Robert Hendley > [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]>