--- Paul Benedict <[EMAIL PROTECTED]> wrote: > I have never seen anyone attach Spring transactional > logic to an action, and called DAOs straight from the > action. That's not good practice, because it mashes > web, business, and data layers all in one place.
Here's my question/comment: to me it seems that the only reason an "Action" would be considered part of the web layer is that S2 maps the names of Actions to URLs and can process the named result types in a webby way. But that's really not related to the Actions themselves--to me this distinction seems the point of XWork/the "Command Pattern". The fact that I can test my Actions in complete isolation only makes me believe that even more--because my test framework is blissfully unaware that it's testing what are, ultimately, URLs. So... while I agree that things should be broken up into fairly granular units of responsibility, I guess I wonder if it's really fair to call Actions part of the web layer anymore, when really they're just being used by (what I consider to be) the *real* web layer? d. ____________________________________________________________________________________ Yahoo! Music Unlimited Access over 1 million songs. http://music.yahoo.com/unlimited --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
