t:inputHtml doesn't work when using it with Custom Object that encapsulates a
String value
---
Key: MYFACES-786
URL: http://issues.apache.org/jira/browse/MYFACES-786
Project: MyFaces
[
http://issues.apache.org/jira/browse/MYFACES-736?page=comments#action_12356903
]
Oliver Rossmueller commented on MYFACES-736:
As Martin pointed out there was a reason why coercion was removed in
ValueBindingImpl.setValue: it is against the
defining attributes in tomahawk.tld makes it difficult to subclass tomahawk
components
--
Key: MYFACES-787
URL: http://issues.apache.org/jira/browse/MYFACES-787
Project: MyFaces
[ http://issues.apache.org/jira/browse/MYFACES-787?page=all ]
Simon Kitching updated MYFACES-787:
---
Attachment: tomahawk.tld.patch
html_column_attributes.xml
defining attributes in tomahawk.tld makes it difficult to subclass tomahawk
[ http://issues.apache.org/jira/browse/MYFACES-785?page=all ]
Grant Smith closed MYFACES-785:
---
Fix Version: Nightly
Resolution: Fixed
Updated the tld.
Docs refer to non-existant spec. section
[
http://issues.apache.org/jira/browse/MYFACES-652?page=comments#action_12356922
]
Grant Smith commented on MYFACES-652:
-
Stephan,
I agree that this would be very useful. However, the way the build.xml files
work on this project, they are all in fact
[
http://issues.apache.org/jira/browse/MYFACES-403?page=comments#action_12356926
]
Grant Smith commented on MYFACES-403:
-
Are FacesMessages the only objects we want to persist across the redirect ? Is
anything else lost that would also benefit from