[
https://issues.jboss.org/browse/JGRP-1860?page=com.atlassian.jira.plugin....
]
Bela Ban edited comment on JGRP-1860 at 7/22/14 3:40 AM:
---------------------------------------------------------
So you want an implementer of a custom marshaller to be able to (re)use the
{{Util.objectToFromBuffer()}} methods, but still be able to pass in a class loader ? This
in order to prevent having to implement something equivalent themselves ? Makes sense, can
you confirm this ?
was (Author: belaban):
So you want an implementer of a custom marshaller to be able to (re)use the
{{Util.objectToFromBuffer()} methods, but still be able to pass in a class loader ? This
in order to prevent having to implement something equivalent themselves ? Makes sense, can
you confirm this ?
Custom classloader in RpcDispatcher
-----------------------------------
Key: JGRP-1860
URL:
https://issues.jboss.org/browse/JGRP-1860
Project: JGroups
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 3.2.13
Reporter: Dennis Reed
Assignee: Bela Ban
Fix For: 3.5
RpcDispatcher is hard-coded to use JGroups' classloader when marshalling the
users's custom objects over RPC.
RpcDispatcher uses Util.objectFromByteBuffer to unmarshall, which uses an
ObjectInputStream. ObjectInputStream uses the classloader of its caller's class
(Util).
RpcDispatcher does allow a custom marshaller to be used (implementing
RpcDispatcher.Marshaller), but since Util.objectFromByteBuffer hard-codes the use of
ObjectInputStream, a custom marshaller cannot simply set the classloader and then delegate
back to the default JGroups code.
Util.objectFromBuffer should be enhanced to use a custom ObjectInputStream implementation
that overrides resolveClass to use a custom classloader, and an API should be added to
RpcDispatcher to pass in the classloader to use.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)