-
1. Re: multile Log4j version
starksm64 Apr 29, 2004 10:25 AM (in response to vinodnair)There is an example of just this scenario in the testsuite. It uses a scoped loader configuration in the war WEB-INF/jboss-web.xml descriptor to load from the war WEB-INF/lib directory before the server's classes:
<?xml version='1.0' encoding='UTF-8' ?> <!DOCTYPE jboss-web PUBLIC "-//JBoss//DTD Web Application 2.3V2//EN" "http://www.jboss.org/j2ee/dtd/jboss-web_3_2.dtd"> <jboss-web> <class-loading java2ClassLoadingCompliance="false"> <loader-repository> jboss.test:war=log4j113.war <loader-repository-config> java2ParentDelegation=false </loader-repository-config> </loader-repository> </class-loading> </jboss-web>
-
2. Re: multile Log4j version
vinodnair Apr 30, 2004 7:55 AM (in response to vinodnair)Thanks a lot Scott.. I tried this but gave an error which said class loader configuration need to be done at the root level..i went through the advanced documentation and found this and removed the class loader entry in the jboss-web.xml and put the following in the jboss-app.xml
<?xml version="1.0" encoding="UTF-8"?>
<jboss-app>
<loader-repository>some.dot.com:loader=sca.ear</loader-repository>
</jboss-app>
and it worked fine. Going ahead in configuration ..we are using xerces for XML uploads and SOAP message verification. We are using the SAX parser. As JBoss makes use of default crimon.jar i started the server with --jaxp=xerces but still my XML upload is giving an error
Feature: http://apache.org/xml/features/validation/schema
Any clue in this regard with be highly helpful...Thanks once again
Regards
Vinod Nair