You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Paul Nicolucci (JIRA)" <de...@myfaces.apache.org> on 2011/09/22 19:57:34 UTC
[jira] [Created] (MYFACES-3316) Problem concerning MyFaces-1890:
does not work when dealing with a composite component
Problem concerning MyFaces-1890: does not work when dealing with a composite component
--------------------------------------------------------------------------------------
Key: MYFACES-3316
URL: https://issues.apache.org/jira/browse/MYFACES-3316
Project: MyFaces Core
Issue Type: Bug
Components: JSR-314
Affects Versions: 2.0.5
Reporter: Paul Nicolucci
I've run into an issue where the fix in MyFaces-1890 does not work.
When dealing with a composite component:
valueBinding.getType(facesContext.getElContext());
returns java.lang.Object since the MapELResolver.getType returns
Object.class in accordance with the EL Spec, the JavaDoc can be found here:
http://java.sun.com/javaee/5/docs/api/javax/el/MapELResolver.html
The fix was made in the following JIRA issue for the TomCat EL:
https://issues.apache.org/bugzilla/show_bug.cgi?id=51177
So in the case of a composite components the MyFaces Implementation still
has an issue.
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 and I'll to a solution to contribute.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira