[
https://issues.apache.org/jira/browse/MYFACES-3259?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13086164#comment-13086164
]
Leonardo Uribe commented on MYFACES-3259:
-----------------------------------------
This is what I have so far. The solution works but looking more carefully this
change should follow the same rules as f:ajax. For example, f:ajax does not
"pass" through composite components, but "pass" over anything else. The strange
thing here is f:validateBean does not have that obvious restriction (but maybe
that restriction does not apply after all). I still don't know what to do in
this case. What we need here is have some examples about what should work and
what shouldn't work, and then implement something according to that.
> Custom Validator tag attributes are not configured when used with default tag
> handler in wrapping mode
> ------------------------------------------------------------------------------------------------------
>
> Key: MYFACES-3259
> URL: https://issues.apache.org/jira/browse/MYFACES-3259
> Project: MyFaces Core
> Issue Type: Bug
> Reporter: Matt Benson
> Attachments: MYFACES-3259-1.patch, MYFACES-3259.tar.gz,
> MYFACES-3259.tar.gz
>
>
> demo forthcoming; it would seem the FaceletCompositionContext would need to
> keep track of the delegate as well as the id of enclosing validators in order
> to be able to apply the xml attributes.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
