I just read "Struts In Action", Chapter 8.4.
I had some pretty clear text related to this topic. However, I'm a little unclear on a couple issues:
1) Generally this is a sign that the business logic is too strongly
coupled with the Action or
2) The Action hierarchy is too shallow
In our situation, it's not desirable for the "exit" action to determine "where to go" and then to have it obtain the necessary object, get it on a form (of a different type I'll add) and then forward to the Tiles
jsp. The domain of object types that might need to be loaded as well as what page to end up on is almost mind numbing in this application. That's why we just have the "exit" action do what it's designed to do and then have it forward to another decision point at which point it can prepare the data for the Tiles rendering.
So given that long winded diatribe
it doesn't feel right to deepen the hierarchy just so two actions can share code since it doesn't feel right that the exit action should be concerned with what comes after it in the flow. So I'm left with item 1 and I don't really know how to apply that statement to see if it holds true in our situation.
Regards,
Matthew Marquand
Object Ovation, Inc.