[
https://issues.apache.org/jira/browse/HADOOP-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12641202#action_12641202
]
Chris K Wensel commented on HADOOP-4467:
----------------------------------------
I probably should have phrased this one differently, but it does seem to be
standard practice to provide the context classloader when calling Class.forName.
I can submit a patch with the one line change. but I do not know if there
should (or even could be) an accompanying unit test for this. please advise.
> SerializationFactory should use current context ClassLoader
> -----------------------------------------------------------
>
> Key: HADOOP-4467
> URL: https://issues.apache.org/jira/browse/HADOOP-4467
> Project: Hadoop Core
> Issue Type: Bug
> Affects Versions: 0.18.1
> Reporter: Chris K Wensel
>
> SerializationFactory#add calls Class.forName without a ClassLoader instance.
> This prevents user-space Serialization classes from being loaded.
> The resulting ClassNotFoundException is eaten after being logged, and a NPE
> is thrown further down the line when a Serializer is requested.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
