I've run into an issue where this fix does not work. When dealing with a composite component:
returns java.lang.Object since the MapELResolver.getType returns Object.class in accordance with the EL Spec, the JavaDoc can be found here:
The fix was made in the following JIRA issue for the TomCat EL:
So in the case of a composite component the MyFaces Implementation still has an issue. I just wanted to make a note on this issue, I can open another JIRA issue if needed.
Could a context parameter be added to set df.setParseBigDecimal(true); so that we can avoid the problem faced here. I think the only reason this was not made the default behavior was to keep some samples from failing or existing applications that depend on the behavior from failing.
I'm willing to create,test and contribute the fix. Please let me know what your thoughts are on this issue.