cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CXF-2025) Null Pointer Exception in AbstractInvoker.createFault()
Date Tue, 10 Feb 2009 20:31:59 GMT

     [ https://issues.apache.org/jira/browse/CXF-2025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Daniel Kulp resolved CXF-2025.
------------------------------

       Resolution: Fixed
    Fix Version/s: 2.1.5
                   2.0.11
         Assignee: Daniel Kulp

> Null Pointer Exception in AbstractInvoker.createFault()
> -------------------------------------------------------
>
>                 Key: CXF-2025
>                 URL: https://issues.apache.org/jira/browse/CXF-2025
>             Project: CXF
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.0.8
>            Reporter: Kaj Kandler
>            Assignee: Daniel Kulp
>             Fix For: 2.0.11, 2.1.5
>
>
> In certain instances (Exceptions coming from WS-I Security interceptor), the Fault can't
be created, because it does throw a null pointer exception.
> Here is at least a safer implementation. Not sure if this really help debugging the issue
underlying why the method seems to be null.
>     protected Fault createFault(Throwable ex, Method m, List<Object> params, boolean
checked) {
>         if (checked) {
>             return new Fault(ex);
>         } else {
>             String message = (ex == null) ? "" : ex.getMessage();
>             String method = (m == null) ? "<null>" : m.toString();
>             return new Fault(new Message("EXCEPTION_INVOKING_OBJECT", LOG, message, method,
params), ex);
>         }
>     }
> This hurts especially it does simply mask what really is happening.

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