Tom Jenkinson [
https://community.jboss.org/people/tomjenkinson] created the discussion
"Re: Transactional MSC"
To view the discussion, visit:
https://community.jboss.org/message/829679#829679
--------------------------------------------------------------
David Lloyd wrote:
> Tom Jenkinson wrote:
>
> Could implementing the classloader approach be achieved by running two separate
subsystems in WildFly, as I understand it that would leverage the classloader isolation
provided by jboss modules?
>
> It might mean binding something new into JNDI in order that MSC can get a reference
to an AtomicAction "factory"/similar but that should be possible.
Nah the class loading is orthogonal to management subsystems. The ArjunaCore bits we
would use for MSC and management would actually not be directly managed by the management
system - at least not overtly. The easiest way to do this is to just introduce another
module (i.e. another copy of the bits) which contains just the parts we want to use for
this.
Hi David,
Sorry, I think I may have used the wrong terminology here, what it turns out I mean is I
wonder if we can prototype (achieve?) the classloader separation using two separate
"JBoss Modules" in WildFly. As you have identified I would expect the same jar
to be present in the two separate "modules" where the "msc" depends on
an "arjunacore:main" module and "transactions subsystem" depends on
the existing "jts:main" module.
Is "JBoss Modules" available at the stage that we would need it, I can
appreciate that subsystems are not.
JNDI would not actually be a requirement. We can have something like:
AtomicActionFactory aaf = AtomicActionFactory.getAtomicActionFactory(String
configurationType);
Thanks,
Tom
--------------------------------------------------------------
Reply to this message by going to Community
[
https://community.jboss.org/message/829679#829679]
Start a new discussion in JBoss Transactions Development at Community
[
https://community.jboss.org/choose-container!input.jspa?contentType=1&...]