This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Is it a good idea or bad idea to use Hibernate or any O/R API with STRUTS? If it is good practice, here is my question. Can you map the STRUTS Form Bean object to the Hibernate Mapping or do you have to create seperate classes, one for STRUTS and one for Hibernate and transfer the data from one to the other? Also, would my action class handle the actual .save() method from the Hibernate API or would I do it somewhere else? I would really like it if someone had some information regarding integrating Hibernate with STRUTS. Thanks.
After some more research I have found that most examples show using the Hibernate API within the Action Handler class of the Form. Since this is where the Form Bean is instantiated and values are assigned, it makes sense. However, should we not also want to seperate this a bit more. And somehow move the DB Access Logic outside of the Action Handler and have another Action called to handle the DB Transactions? I don't know, I am just looking for ideas here. Any suggestions? [ June 03, 2003: Message edited by: Gregg Bolinger ]
Do you consider using JDO for data assess? If I understand you right - you try to make application architecture without visible "model" layer. You data go between database and forms bypassing intermediate object layer. This is reasonable design, but you lose some degree of flexibility and loitering your controller layer with data assess logic. Best, Igor.