You deploy two different applications to the WebLogic container. One application use Xerces parser version A and the other application uses Xerces parser version B. Both these versions are different…

Question

Options

• AModify the applications to use the same version that WebLogic uses internally.
• BBased on available examples of Filtering Classloader entries, try to modify get the proper entries.
• CDeploy and use the Classloader Analyzing Tool to resolve all conflicts with conflicting libraries.
• DSplit the application into separate WebLogic containers and use different WLS versions of Xerces
• ELook for a WebLogic release that uses the same version of Xerces that the applications use.

• B
  84% (32)
• C
  8% (3)
• D
  3% (1)
• E
  5% (2)

Explanation

• The FilteringClassLoader provides a mechanism for you to configure deployment descriptors to explicitly specify that certain packages should always be loaded from the application, rather than being loaded by the system classloader. This allows you to use alternate versions of applications such as Xerces and Ant. * To configure the FilteringClassLoader to specify a certain package is loaded from an application, add a preferapplicationpackages descriptor element to the weblogicapplication.xml which details the list of packages to be loaded from the application. The following example specifies that org.apache.log4j.* and antlr.* packages are loaded from the application, not the system classloader: <preferapplicationpackages> <packagename>org.apache.log4j.</packagename> <packagename>antlr.</packagename> </preferapplicationpackages>

No community discussion yet for this question.