On 9/7/06, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
Michael Jouravlev ha scritto:
> Using actions is a totally legitimate way to build composite page.
I disagree, to build composite pages I will use "composite view" pattern
implementation, such as Tiles and Sitemesh.
I think that using actions as a way to build composite page breaks the
MVC pattern, because actions are not designed for this use.
Is this the only argument you have, "because actions are not designed
for this use"? You can do better than that ;-)
Dynamic inclusion is a legitimate JSP feature. It is possible to
include any resource, not just a JSP file. The only difference between
including a JSP file and including a Struts action is extra
Struts-related processing. The filters will (or will not) be executed
again both for JSP file and for Struts action. So the fuss is only
about Struts processing chain. I never had problems with that, maybe
my applications are too simple to be affected by that :) Martin says
that there might be some gnarly bits, have anyone come across those
bits or they are pure theoretic fears?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
