Annother middle way would be to use the "plain text result" and no separate class attribute like this
<action name="intro" > <interceptor-ref name="myAuth"/> <result type="plaintext">/intro.html</result> </action> Advantages: -no own Action class (ActionSupport is used) -your static resources don't get processed which should save time -you can still your Security interceptors to check the Authentication and Authorization of the user /Stephan > >> Roger wrote: > >> > Having followed this group for a while I know that the generally > >> accepted > >> > wisdom is that every page should be handled via an Action. However, I > >> > have an application that is probably going to be 70% static pages > with > >> > 30% Strut-able actions to handle form entry etc etc. This means that > >> I'm > >> > going to have an awful lot of action classes that do nothing other > than > >> > display the next page which feels kludgy. How would people deal with > >> > this? > >> > > >> > Regards -- GMX startet ShortView.de. Hier findest Du Leute mit Deinen Interessen! Jetzt dabei sein: http://www.shortview.de/[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
