[
https://issues.apache.org/jira/browse/ADFFACES-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matthias Weßendorf updated ADFFACES-175:
----------------------------------------
Fix Version/s: 1.0.0-incubating-core
Affects Version/s: 1.0.0-incubating-core
> Default FacesBean types to UIXFacesBeanImpl and UIXEditableFacesBeanImpl
> ------------------------------------------------------------------------
>
> Key: ADFFACES-175
> URL: https://issues.apache.org/jira/browse/ADFFACES-175
> Project: MyFaces ADF-Faces
> Issue Type: Improvement
> Affects Versions: 1.0.0-incubating-core
> Reporter: Adam Winer
> Assigned To: Adam Winer
> Fix For: 1.0.0-incubating-core
>
>
> The current faces-bean.properties defaults the FacesBean type to
> UINodeFacesBean. That was a reasonable choice back when the vast majority of
> renderers went through the old UIX codebase, but now just the opposite is
> true. As a result, anyone writing a new renderer gets an unnecessarily heavy
> FacesBean (and pulls in the UIX code) unless they explicitly add an entry to
> faces-bean.properties. Also, I don't think we have a good default for
> UIXEditableValue, so developers that write a renderer for an editable
> component have to remember to use UIXEditableFacesBeanImpl or they get a
> cryptic problem.
> Anyway, we should:
> - Make UIXFacesBeanImpl the default in Trinidad
> - Make UIXEditableFacesBeanImpl the default for
> org.apache.myfaces.trinidad.component.UIXEditableValue
> - Switch everything that still really does need to use UINodeFacesBean (or a
> subclass)
> to do so explicitly, on a per-renderer-type basis (not at a component
> class level)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
