If users want to run Ceylon using JBoss modules we have two options:
This is from Ceylon running under JBoss modules, and so it is already set up, and in theory we don't have much to do but load the module and run it, right?
This is from Java not running under JBoss modules and we need to set it up.
-- Well, actually we have two cases: the distrib modules are already in the classpath, set by the user, or
-- They are not and we need to either call or do like Launcher
The problem ATM with JBoss modules is that it completely fucks up JAXP system-wise. The minute we load JBoss modules, it hijacks the JAXP system properties with its own classes, that only its own classloader can provide. This is wrong, as it kills every other thread running on the JVM that wants to use JAXP (if they are not using JBoss modules).
I guess the first thing would be to ask the JBoss modules guys if we can do something about not fucking up JAXP system-wise, and upgrade our JBoss modules lib when they add that option.
FroMage
commented
9 years ago
If users want to run Ceylon using JBoss modules we have two options:
LauncherThe problem ATM with JBoss modules is that it completely fucks up JAXP system-wise. The minute we load JBoss modules, it hijacks the JAXP system properties with its own classes, that only its own classloader can provide. This is wrong, as it kills every other thread running on the JVM that wants to use JAXP (if they are not using JBoss modules).
I guess the first thing would be to ask the JBoss modules guys if we can do something about not fucking up JAXP system-wise, and upgrade our JBoss modules lib when they add that option.