From 5f4c9d997ab5ebc8deb5ded4e4d1ccb9daf36978 Mon Sep 17 00:00:00 2001 From: Arjen Poutsma Date: Tue, 13 Feb 2007 22:52:55 +0000 Subject: [PATCH] Started on FAQ --- src/site/apt/faq.apt | 59 ++++++++++++++++++++++++++++++++++++++++++++ src/site/site.xml | 5 ++-- 2 files changed, 62 insertions(+), 2 deletions(-) create mode 100644 src/site/apt/faq.apt diff --git a/src/site/apt/faq.apt b/src/site/apt/faq.apt new file mode 100644 index 00000000..5b9b4b8f --- /dev/null +++ b/src/site/apt/faq.apt @@ -0,0 +1,59 @@ + -------------------------- + Frequently Asked Questions + -------------------------- + +Frequently Asked Questions + + Below are some questions that are frequently asked on the Spring-WS forum. + Please read this page before you ask a question on the forum. + +* Java + + <> + + Yes it does, but it requires some work. Java 1.4 is bundled with the older XML parser Crimson, which does not handle + namespaces correctly. Additionally, it is bundled with an older version of Xalan, which also has problems. + Unfortunately, placing newer versions of these on the classpath does not override them. + See {{{http://xml.apache.org/xalan-j/faq.html#faq-N100D6}this FAQ}} entry on the Xalan site, and also + {{{http://xerces.apache.org/xerces2-j/faq-general.html#faq-4}this entry}} on the Xerces site. + + The only solution that works is to add newer versions of Xerces and Xalan in the lib/endorsed directory of your JDK, + as explained in those FAQs. + +* SAAJ + + <> + + SAAJ is the SOAP with Attachments API for Java. Previously, it has been part of JAXM, but it has been released as a + seperate API as part of the {{{http://java.sun.com/webservices/jwsdp/index.jsp}Java Web Service Developer Pack}}, + and also as part of J2EE 1.4. SAAJ is generally known as the package <<>>. + + <> + + See below: + +*--------------------+--------------+ +| Application Server | SAAJ Version | +*--------------------+--------------+ +| BEA WebLogic 8 | 1.1 | +| BEA WebLogic 9 | 1.2 | +| IBM WebSphere 6 | 1.2 | +| SUN Glassfish | 1.3 | +*--------------------+--------------+ + + <> + ++--------------- +java.lang.NoSuchMethodError: javax.xml.soap.MessageFactory.newInstance(Ljava/lang/String;)Ljavax/xml/soap/MessageFactory; ++--------------- + + <> + + Like most J2EE libraries, SAAJ consists of two parts: the API that consists of interfaces (<<>>), + and the implementation (<<>>). + The stacktrace is due to the fact that you are using a new version of the API (SAAJ 1.3), while your application + server provides an earlier version of the implementation (SAAJ 1.2 or even 1.1). Spring-WS supports all three + versions of SAAJ (1.1 through 1.3), but things break when it sees the 1.3 API, while there is no 1.3 implementation. + + The solution therefore is quite simple: to remove the newer 1.3 version of the API, from the classpath, and replace + it with the version supported by your application server. diff --git a/src/site/site.xml b/src/site/site.xml index e2b05951..6f510cbe 100644 --- a/src/site/site.xml +++ b/src/site/site.xml @@ -7,10 +7,11 @@ - - + + +