HI Tomasz,
I know very little about java.endorsed.dirs, but if it is a JVM property,
then it is common to all Kepler modules as all JVM properties
are common to the instance of the JVM.
Maybe the Java ClassLoader can be manipulated to do what you
want, but I don't know how it would be done.
I vaguely remember that there was a way to have multiple JVMs
in one process, but I could not find a reference to that. Multiple JVMs
would allow multiple properties, though you would need to use
some sort of Remote Method Invocation (RMI) to communcate.
This seems very heavy handed.
_Christopher
On 1/18/13 2:29 AM, Tomasz Żok wrote:
Dear Kepler Team,
I am developing a module which requires a correct setting of java.endorsed.dirs
property. It is a JVM setting so it is not sufficient to add a line in:
mymodule/resources/system.properties/endorsed.properties
I have found that there are two possibilites:
1. ant run -Dproperties=java.endorsed.dirs=<...>
2. ant run -Dmodule=mymodule
However both of them will modify java.endorsed.dirs globally for the whole JVM.
Is there a possibility to specify it in a way that only a single module is
affected? There is a method to enforce a different classloader for a module so
maybe this can be used somehow?
Generally I think it would be nice to have a feature that java.endorsed.dirs is
totally configurable by module. Developer would be then responsible for
configuring it inside of his module/resources/. Is this at all possible in the
current way Kepler loader works? Or maybe Java itself disallows such thing?
Best regards,
Tomasz Zok
--
Christopher Brooks, PMP University of California
CHESS Executive Director US Mail: 337 Cory Hall
Programmer/Analyst CHESS/Ptolemy/Trust Berkeley, CA 94720-1774
ph: 510.643.9841 (Office: 545Q Cory)
home: (F-Tu) 707.665.0131 cell: 707.332.0670
_______________________________________________
Kepler-dev mailing list
[email protected]
http://lists.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-dev
