[ http://issues.apache.org/jira/browse/MYFACES-210?page=comments#action_12357433 ]
Adam Winer commented on MYFACES-210: ------------------------------------ The spec is unclear, not incorrect. "may be configured" means "programatically from the Java API", or "by an attr on the JSP tag" - not by faces-config.xml. And there really isn't any ambiguity - there's no <value> element inside <attribute> or <property>, so how are you supposed to set anything??? Note that <default-value> merely refers to the default if nothing is set, which is to support tools. You cannot configure properties on a converter instance from faces-config.xml. > Undesired dependency on ApplicationImpl in FacesConfigurator > ------------------------------------------------------------ > > Key: MYFACES-210 > URL: http://issues.apache.org/jira/browse/MYFACES-210 > Project: MyFaces > Type: Bug > Components: Implementation > Versions: 1.0.9m9 > Environment: Custom ApplicationFactory and Application Objects > Reporter: Walter Snel > Assignee: Martin Marinschek > Priority: Minor > > Manfred's recent additions related to the configurability of Converters > created a dependency on a particular Application implementation in the > FacesConfigurator. > I noticed this because I'm using a custom ApplicationFactory that returns a > custom Facade (with augmentations) to the ApplicationImpl class. > In this case the FacesConfigurator doesn't call the > addConverterConfiguration. This, later on, leads to horrible nullpointer > exceptions when any of standard converters are used. Perhaps we could > consider using relfection instead of the current 'instanceof' mechanism to > find out if the addConverterConfiguration() method is supported ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
