[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [higgins-dev] Re: [Bug 190604] Allow context providers to be loaded by a unique classloader
|
Hi,
As I opened that bug, I can clarify. The CP can use
libraries that
are clashing with the Higgins libraries. For example, the
STS uses
Axis bindings which prevents CPs to use Axis2 as a WS stack
to contact
its identity stores and is forced to use whatever comes
with the STS
for compatibility.
What is the best solution is to "isolate" the CP in its own
unique
classloader. Obviously, it is not only up to the CP to
implement it
as it has to be managed from the CP
context.
For example of such architectural model, see how Axis2
modules are
implemented - each
module is "isolated" from the others using own
classloader created by and
managed by the Axis2 engine that loads them.
Same model is applied to their sevice packages (aar
files).
The
Higgins CPs have a "plugin flavor" to them which calls for
such
design.
George
Hi all,
The summary of this bug says "Allow context providers
to be loaded by a unique classloader".
I'm not sure what 'unique' means
here. Does it simply mean that it should be possible to specify the classloader
to be used?
If yes, I am going to close the bug.
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.
**********************************************************************