cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From andymc12 <>
Subject [GitHub] cxf pull request #270: CXF-7349: NPE when thread context classloader is null
Date Thu, 27 Apr 2017 21:14:03 GMT
GitHub user andymc12 opened a pull request:

    CXF-7349: NPE when thread context classloader is null

    A null context classloader is valid - it means that the JVM's boot classloader is the
context.  When using the ClassLoaderUtils class, there are a few places where we get the thread's
context classloader, but don't check it for null before invoking methods on it - such as getResource/getResources/etc.
    This change ensures that we get a non-null classloader by using the system classloader
when the current thread context classloader is null.  

You can merge this pull request into a Git repository by running:

    $ git pull NPE-ClassLoaderUtils

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #270
commit 751e63ac9fdf5752ae3956b84925ec91ea6e0253
Author: Andy McCright <>
Date:   2017-03-01T22:40:02Z

    Merge pull request #4 from apache/master

commit eec3cd484749630e599732a082e45d60ef1d10d7
Author: Andy McCright <>
Date:   2017-04-05T14:48:33Z

    Merge branch 'master' of

commit 8f38958d75d23edb9b711b6d9c77e663091412ab
Author: Andy McCright <>
Date:   2017-04-20T20:14:20Z

    Merge branch 'master' of

commit cb14bf9ac392a7936aff08d7e54dd12720f8e733
Author: Andy McCright <>
Date:   2017-04-27T20:57:26Z

    Merge branch 'master' of

commit 7043ded41dc7484a9c47b38888a191ee70802c11
Author: Andy McCright <>
Date:   2017-04-27T21:09:55Z

    CXF-7349: Resolve NPE when TCCL is null


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message