David H. DeWolf wrote:
That said, didn't I read somewhere that we're moving towards getting
rid of struts.properties? Wouldn't it be easier and more consistent
to just add the following to struts.xml:
<result-selector class="o.a.s.dispatcher.ContentTypeResultSelector"/>
Seems to me like this type of configuration is very similar to the
interceptor configuration and should be designed similarly.
Actually, I'd prefer we went the other direction, get rid of the need
for struts.xml, but maybe that's just me. The question is if they need
to be configured on a package/action basis. If they can be done
globally, then struts.properties is the better place. Otherwise,
struts.xml would be a better fit.
If we used the <result-selector> element, how would you define multiple
ones? Just repeating the element wouldn't match the style of other
configuration elements. How would this look as one or more annotations?
Don
David
Don
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]