[
https://issues.apache.org/jira/browse/MYFACES-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831994#action_12831994
]
Martin Koci commented on MYFACES-2536:
--------------------------------------
Yes, ugly exceptions happen with <f:converter binding="#{aNonExistentBean}" />:
1) myfaces: NPE in ConvertDelegateHandler
2) mojarra: javax.faces.view.facelets.TagException: /test.xhtml <f:converter>
Default behavior invoked of requiring a converter-id passed in the constructor,
must override ConvertHandler(ConverterConfig)
Is seems that this odd behaviour comes from old facelts codebase. I try to find
out how those converterId/binding attributes should cooperate.
> converterId and validatorId should not be required
> --------------------------------------------------
>
> Key: MYFACES-2536
> URL: https://issues.apache.org/jira/browse/MYFACES-2536
> Project: MyFaces Core
> Issue Type: Bug
> Components: JSR-314
> Affects Versions: 2.0.0-beta-2
> Environment: myfaces core trunk
> Reporter: Martin Koci
> Priority: Trivial
> Attachments: MYFACES-2536.patch
>
>
> With JSF 2.0 attributes converterId resp. validatorId (tags f:converter resp.
> f:validator) aren't required. See:
> https://javaserverfaces.dev.java.net/nonav/docs/2.0/pdldocs/facelets/f/converter.html
> https://javaserverfaces.dev.java.net/nonav/docs/2.0/pdldocs/facelets/f/validator.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
