Hi,
Since I submitted that
enhancment request, we at ALF have implemented a custom classloader the loads
and runs our RP agent
in isolation (since being
a servlet filter we don't want the RP libraries to interfere with the protected
application libraries - situation
very similiar to the
context providers).
We ran into two areas of
"trickiness" :
* anything returned from
objects instantiated in the "isolation" classloader must be proxied
to
instances in
the calling classloader
* if the isolating
classloader must not load JCE providers (for example axis2 and
xml-security
rely on
Bouncy Castle and load it in java.security.Security) in the global
registry
We would be happy to contribute it alongside with the
corresponding know-how expertise
to Higgins whenever it is
ready to be implemented. Let me know whenever about to do it and
I will try to help with
whatever I could.
Best
Regards,
George
All,
The thread that spawned this bug is here.
If I had been a exceptional Higgins citizen, I would have logged similar
defects for any Higgins component which has the ability to load "pluggable modules". I wasn't being exceptional, so I only did the one for
IdAS. I'm still not being exceptional, so I'm only assuming that as this
applies to these other components, their owners will make sure the issue
gets addressed somehow.
Jim
>>> "Markus Sabadello" <msabadello@xxxxxxxxxxxxx> 7/20/07 10:52 AM >>> Hi all,
I'm a bit new to this bug processing.. I just changed the status of this one to
"ASSIGNED".
Actually what this bug says "Allow context providers to be
loaded by a unique classloader" is possible with my new IdASRegistry.. There's a
method that lets you set the class loader to be used for instantiating context
factories.
I guess I wait a bit more until my stuff has been reviewed /
adjusted / integrated with IdAS and then change it to
"RESOLVED".
Markus
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
|