myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Marinschek (JIRA)" <...@myfaces.apache.org>
Subject [jira] Commented: (MYFACES-2607) Ugly NPE in CompositeFunctionMapper.resolveFunction() if second FunctionMapper is null
Date Wed, 17 Mar 2010 09:12:27 GMT

    [ https://issues.apache.org/jira/browse/MYFACES-2607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12846353#action_12846353
] 

Martin Marinschek commented on MYFACES-2607:
--------------------------------------------

Hi jakob,

sure, sure - my comment was purely theoretical, if the second part of your statement would
have been true.

In any case, I think I like the NoopFunctionMapper a bit more than passing null - it sounds
like a good thing to do to tell people: there is nothing, but this is good as it is.

best regards,

Martin

> 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.


Mime
View raw message