Subject:Dont use System.setProperty in java code generation of Enterprise Edition Author:Rudolf P Weinmann Date:30 Jun 2005 12:49 AM Originally Posted: 30 Jun 2005 12:50 AM
I like the ability to generate java code for xslt transformations. What IMO should be amended though, is the use of System.setProperty, because it changes the environment at runtime for *ALL* applications running in the same jvm. If for example one application needs to run with saxon and the other with xalan and both make use of System.setProperty to set the transformerFactory, then you will run into trouble. Also if bindir, rootdir and appdata are set this way, I get a problem, because only one of the applications (the one that executed the first) gets configured properly and all others pick up the same settings, which might not be what's needed. Which of the applications run first is by chance. I would be glad, if you'd provide a better solution.