From cb70abfc87805066a1700264f99a0d4007fb5364 Mon Sep 17 00:00:00 2001 From: Arjen Poutsma Date: Fri, 14 Mar 2008 10:50:23 +0000 Subject: [PATCH] SWS-312 --- src/site/fml/faq.fml | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) diff --git a/src/site/fml/faq.fml b/src/site/fml/faq.fml index e6db9ed8..f073e71d 100644 --- a/src/site/fml/faq.fml +++ b/src/site/fml/faq.fml @@ -190,6 +190,37 @@

+ + + Does Spring-WS run on IBM WebSphere? + + +

+ WebSphere bundles some libraries which are out-of-date, and need to be upgraded with more recent + versions. Specifically, this includes XML-apis, Xerces, Xalan, and WSDL4J. +

+

+ There are a couple of ways to upgrade these libraries, all using parent-last or application-first + classloading. +

    +
  • + Package the libraries as part of the WAR (in WEB-INF/lib), and run the web application with + the parent-last (application-first) classloading. +
    • +
  • + Package the libraries as part of the EAR, add class-path entries to the manifest of the web + application, and run the entire application with the parent-last classloading. +
    • +
  • + Create a new classloader in the WebSphere console, and associate the libraries with. Set + this classloader to parent-last. +
    • +
+ The last approach has the advantage of restricting the parent-last classloading to the conflicting + libraries only, and not to the entire application. +

+ + WSDL