[
https://issues.apache.org/jira/browse/MYFACES-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845967#action_12845967
]
Jakob Korherr commented on MYFACES-2607:
----------------------------------------
Hi Martin,
It has to be determined (and actually I'm working on it right now) if the null
value is ok here ore not. If it is ok, we have to get rid of the NPE (as I
did), otherwise we have to check for a null-value in the constructor and throw
a IllegalStateException there. As I said, I'm currently working on that.
Regards,
Jakob
> Ugly NPE in CompositeFunctionMapper.resolveFunction() if second
> FunctionMapper is null
> --------------------------------------------------------------------------------------
>
> Key: MYFACES-2607
> URL: https://issues.apache.org/jira/browse/MYFACES-2607
> Project: MyFaces Core
> Issue Type: Task
> Components: JSR-314
> Affects Versions: 2.0.0-beta-3
> Reporter: Jakob Korherr
> Assignee: Jakob Korherr
> Priority: Minor
> Fix For: 2.0.0-beta-3
>
>
> The class CompositeFunctionMapper gets two FunctionMappers in the constructor
> which it uses to resolve EL functions in its method resolveFunction().
> Currently the first FunctionMapper is always NamespaceHandler and the second
> one is the one from the ELContext, which is null at all times. I think this
> is also a problem, but at first I want to get rid of this ugly NPE.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
