[
https://issues.apache.org/jira/browse/ADFFACES-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Adam Winer updated ADFFACES-477:
--------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
Removing _CAN_COERCE altogether did in fact introduce problems, like putting
back String coercion, and without code changes breaks the use of converter ID
strings for the "converter" property.
For now, hardcoding the two types UIComponent and Converter.
Also, added <coerceStrings> configuration property to (per-project) enable
coercion of strings.
Finally, updated the component generation code so that "converter" wouldn't
crap out - the trick is using getExpressionString() instead of getValue(null)
to retrieve the string when ValueExpression.isLiteralText() is true.
> ADF-Faces plugin companion JIRA for MYFACES-1598 (opened by Bruno Aranda)
> -------------------------------------------------------------------------
>
> Key: ADFFACES-477
> URL: https://issues.apache.org/jira/browse/ADFFACES-477
> Project: MyFaces ADF-Faces
> Issue Type: Bug
> Components: Plugins
> Affects Versions: 2.0.0-incubating-plugins-SNAPSHOT
> Reporter: Tim McConnell
> Assigned To: Tim McConnell
> Fix For: 2.0.0-incubating-plugins-SNAPSHOT
>
> Attachments: ADFFACES-477-2.patch, ADFFACES-477.patch
>
>
> For "binding" the deferred-type must be 'javax.faces.component.UIComponent'
> For "converter" the deferred-type must be 'javax.faces.convert.Converter'
> Now the deferred-type tags in the tld for these attributes are empty (hence
> expeting java.jang.Object)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
