[
https://issues.apache.org/jira/browse/MYFACES-3797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13788125#comment-13788125
]
Gerhard Petracek commented on MYFACES-3797:
-------------------------------------------
it breaks 3rd party libs which check the types of converters and validators.
in most cases i've seen so far they don't expect the need of such check, if
they created the converters and validators internally.
@performance as mentioned before we can tweak the default case (e.g. caching
the info if the feature is enabled. it's currently a first draft and not a
fully optimized final version). if you enable it, you only have a minor
overhead which is smaller than the overhead you get with an external container
(you know the numbers).
however, if it is the only issue, we can change that part to an adapter in some
min., because the rest is the same.
> cdi support for converters and validators
> -----------------------------------------
>
> Key: MYFACES-3797
> URL: https://issues.apache.org/jira/browse/MYFACES-3797
> Project: MyFaces Core
> Issue Type: New Feature
> Components: JSR-344
> Reporter: Gerhard Petracek
> Assignee: Gerhard Petracek
> Attachments: MYFACES-3797.patch
>
>
> with
> <context-param>
>
> <param-name>org.apache.myfaces.CONVERTER_INJECTION_ENABLED</param-name>
> <param-value>true</param-value>
> </context-param>
> and
> <context-param>
>
> <param-name>org.apache.myfaces.VALIDATOR_INJECTION_ENABLED</param-name>
> <param-value>true</param-value>
> </context-param>
> it should be possible to enable cdi support for converters/validators.
> we need the config, because it was postponed for the spec.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
