|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
25/Sep/06 12:14 AM
|
| Labels: |
|
|
When we changed the classloading structure in the 1.0-beta1 we put the EJB's out of reach of the EjbRequestHandler that deserializes remote calls coming into the system. The EjbRequestHandler needs to grab the classloader for the Deployment making the call and continue deserializin.
The trickiest part of the whole thing is you dont know what classloader to use till you've read the deploymentId from the stream then you have to hold on, go grab that deployment instance, grab it's classloader, set it on the EJBObjectInputStream then finish deserializing (i.e. read off the arguments and method and stuff). You can't deserialize everything till you know what classloader to use.
|
|
Description
|
When we changed the classloading structure in the 1.0-beta1 we put the EJB's out of reach of the EjbRequestHandler that deserializes remote calls coming into the system. The EjbRequestHandler needs to grab the classloader for the Deployment making the call and continue deserializin.
The trickiest part of the whole thing is you dont know what classloader to use till you've read the deploymentId from the stream then you have to hold on, go grab that deployment instance, grab it's classloader, set it on the EJBObjectInputStream then finish deserializing (i.e. read off the arguments and method and stuff). You can't deserialize everything till you know what classloader to use.
|
Show » |
|
Bug
Closed
Major
Recent classloader changes break remote server