Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I asked this question in several flavors, and I think I’m not asking the right question. I’m suspecting now that Xalan, since it’s implementing a Java endorsed standard, can only have one implementation at a given VM / ClassLoader.
So is it true? can’t 2 Xalan implementaions “live” in the same System ClassLoader? Or if they can, How?
This seems to be the surprising answer:
For each Xalan implementation use a seperate classloader, and add a file in
META-INF\services\calledEdit it and put it’s only content the Xalan implementation the class loader will use, e.g.:
NOTE: The nice thing here is that as opposed to the regular class loading delegation,
META-INF\servicesis being searched in the current class loader first, where as classes are being search in the parent, then system, and only then in the child classloder