You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Vlasov Igor (JIRA)" <ji...@apache.org> on 2007/10/22 11:32:40 UTC
[jira] Commented: (WW-2209) struts-2.0.dtd incorrectly permits
param element child of default-interceptor-ref
[ https://issues.apache.org/struts/browse/WW-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_42438 ]
Vlasov Igor commented on WW-2209:
---------------------------------
Hello.
I want to change excludeMethods parameter for validationInterceptor in defaultStack.
For whole package I tried:
<default-interceptor-ref name="defaultStack">
<param name="validation.excludeMethods">input,delete,browse
<param name="workflow.excludeMethods">input,delete,browse
</default-interceptor-ref>
and this does not work.
This is because "XmlConfigurationProvider in XWork2 doesn't appear to process parameters for interceptors referenced this way. "
How can I change excludeMethods parameter for validationInterceptor in defaultStack.
Thank you very much for answer..
> struts-2.0.dtd incorrectly permits param element child of default-interceptor-ref
> ---------------------------------------------------------------------------------
>
> Key: WW-2209
> URL: https://issues.apache.org/struts/browse/WW-2209
> Project: Struts 2
> Issue Type: Bug
> Components: Configuration
> Affects Versions: 2.0.11
> Reporter: Joe Germuska
> Assignee: Don Brown
> Priority: Trivial
> Fix For: 2.0.12
>
>
> Can someone just double-check me here, since I'm relatively green on XWork: the struts-2.0 dtd (and the xwork-2.0.dtd) both have this:
> <!ELEMENT default-interceptor-ref (param*)>
> but the XmlConfigurationProvider in XWork2 doesn't appear to process parameters for interceptors referenced this way.
> The fix would be to change the DTD to read
> <!ELEMENT default-interceptor-ref EMPTY>
> I'll gladly make the fix in Struts, but I can't make the fix in XWork. It looks as thought this may also apply to default-action-ref although that isn't where I encountered the problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.