[
https://issues.apache.org/jira/browse/MYFACES-2499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakob Korherr resolved MYFACES-2499.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0-alpha-2
Committed solution for this. However this may not work with PSS. We have to
figure that out later, when Mojarra does.
Also the spec isn't very clear about multiple <f:validateBean> tags. So MyFaces
currently behaves differently from Mojarra in the following scenario:
<h:inputText>
<f:validateBean disabled="true"/>
<f:validateBean />
</h:inputText>
MyFaces does not add the second <f:validateBean />, because the first one is
disabled, Mojarra does. But I think the spec is very clear here: "if the
disabled attribute is true, the validator should not be added. in addition, the
validatorId, if present, should be added to an exclusion list on the parent
component to prevent a default validator with the same id from beeing
registered on the component." However, I added a FIXME in the code.
> f:validateBean disabled="true" not processed correctly
> ------------------------------------------------------
>
> Key: MYFACES-2499
> URL: https://issues.apache.org/jira/browse/MYFACES-2499
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0-alpha-2
> Reporter: Jakob Korherr
> Assignee: Jakob Korherr
> Fix For: 2.0.0-alpha-2
>
>
> In the following scenario the bean validator should not be applied for the
> h:inputText.
> <h:inputText value="#{bean.text2}">
> <f:validateBean disabled="true" />
> </h:inputText>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
