In this case you would need to subclass of ActionMapping, and specify
'type' in <action-mapping> or 'className' in every Action.
Then you would need to subclass RequestProcessor to provide the required
headers.
I could be done by subclassing ActionForward too :
<forward name="something" path="/some/path" className="CachingActionForward">
<set property ..../>
</forward>
PD: I looks like that in Struts 1.1 ForwardConfig is used instead of
ActionForward to configure a forward.
Should className in <forward /> be a subclass of ForwardConfig?
El Lun 23 Sep 2002 17:57, Eddie Bush escribió:
> What I meant is that you will only be able to use the attributes
> declared in the DTD for the <action> tag. For any other properties you
> need to set, you'll have to use <set-property> elements inside of your
> action:
>
> <action ...>
> <set-property .../>
> </action>
>
> I think my first explaination was as clear as mud. Hopefully this
> states it more clearly (so someone will help me rectify my
> misinterpretation, if nothing else!)
>
> Eddie Bush wrote:
> > It would be simple to subclass Action and add the properties. The
> > only problem is that digester is only going to set the properties for
> > the action you subclass (the one in the DTD -- this is how I
> > understand it), so you'll have to nest some <set-property> elements
> > into your action to configure your custom attributes.
> >
> > Someone please correct me if I am wrong :-)
> >
> > David Graham wrote:
> >> All browsers do not listen to the nocache meta tag, which is what I
> >> think you're talking about. Even IE doesn't read that tag properly.
> >> So, it may not be worth the effort to add this to struts. Your
> >> struts actions classes could add the nocache header to the response
> >> before sending which would acheive what you want just not through
> >> struts-config.xml.
> >>
> >> Dave
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
