Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cxf.apache.org
Date: Tue, 30 Jun 2015 17:58:06 +0000 (UTC)
From: "Ravi Luthra (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12841754.1435687076000.60912.1435687086761@Atlassian.JIRA>
In-Reply-To: <JIRA.12841754.1435687076000@Atlassian.JIRA>
References: <JIRA.12841754.1435687076000@Atlassian.JIRA>
 <JIRA.12841754.1435687076198@arcas>
Subject: [jira] [Created] (CXF-6480) InjectionUtils
 createThreadLocalServletApiContext better error message for invalid
 @Context classes
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ravi Luthra created CXF-6480:
--------------------------------

             Summary: InjectionUtils createThreadLocalServletApiContext better error message for invalid @Context classes
                 Key: CXF-6480
                 URL: https://issues.apache.org/jira/browse/CXF-6480
             Project: CXF
          Issue Type: Bug
         Environment: All OS
            Reporter: Ravi Luthra


When you have an \@Context field in a JAXRS class (maybe JAXWS too?) there is a select list of possible proxy classes. This method checks for the proxy class using an if/else/if/else... structure, but there is no final else clause with a good exception. Instead the method attempts to instantiate a null class name (proxyClassName), which throws a NullPointerException. This leaves the method wrapped inside a RuntimeException. A common forgetful change someone might make is to add
{code}@Context private HttpSession session; //(instead of private HttpServletRequest){code}

Which leaves a massive stack trace leaving just an NPE and Spring also tends to obscure the stack-trace of this issue. A better error would be to suggest that the given class ...HttpSession is not a valid Context type. No proxy classes can be created for this type.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)