As my last post mentioned, Hibernate is being used as the persistence mechanism, so persisting the action w/properties is equivalent to persisting a bean. I do have a few reservations.
1) How would you deal with two different objects in a form. I'm guessing save all of their properties avoiding name collisions and then mapping them into the two separate object. Essentially the same as using formbeans, but relieves the template from having to know about the underlying object model.
2) I can't think of a situation off hand where this would happen, but what if two actions that worked with the same business entity both needed to persist it. Even if they extended the same base class, I would either have to specify mappings for both of them into the same table or chain them together and allow only one of them to persist. (This might be more of a Hibernate question).
To sum it all up, is there any reason to _not_ use a formbean? It seems the only reason to not use it is because you don't have to. Does that sound right?
Anoop
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
