>From the FAQ:
Can Apache Soap 2.2 be installed with WebLogic 6.1beta?
The short answer is "yes", but you may have to resolve a namespace conflict
because SOAP 2.2 now uses JAXP (instead of using Xerces directly).
When using Xerces directly there is no problem (other than to have the
correct version first in the classpath). When using JAXP there are two
property values which tell JAXP which parser to use. WL changes these to
their bundled Xerces parser (which is found in weblogic.apache.xerces -- at
least in WL6.0). With the entries described below, you change them to the
original Xerces. If WL6.1 has the bundled Xerces in org.apache.xerces you
also have to have the original xerces.jar first in classpath, otherwise it
should not matter. So the problem is that WL by default uses their bundled
Xerces as JAXP parser.
If you get Unable to resolve namespace, here's how to resolve the conflict:
Put Xerces in front of WebLogic's classpath (in startWebLogic script):
set
CLASSPATH=E:\apache\xerces-1_4_0\xerces.jar;.\lib\weblogic_sp.jar;.\lib\webl
ogic.jar
(Starting with WebLogic 6.1beta, you may have to proceed with Setp #2
below.)
Configure WebLogic to use the same Xerces as Soap, using the WebLogic
console:
mydomain/Services/XML => Configure a new XML Registry...
Name = Xerces JAXP
DocumentBuilderFactory = org.apache.xerces.jaxp.DocumentBuilderFactoryImpl
SAXParserFactory = org.apache.xerces.jaxp.SAXParserFactoryImpl
Transformer Factory = weblogic.apache.xalan.processor.TransformerFactoryImpl
[default]
When To Cache = "cache-on-reference" [default]
mydomain/Servers/myserver => "Services" tab / "XML" tab
Select "Xerces JAPX" from "XML Registry" pulldown
Step 2 results in these changes to WebLogic's config.xml:
Note the new XMLRegistry-attribute in the Server-tag:
<Server
ListenPort="7001"
Name="myserver"
NativeIOEnabled="true"
TransactionLogFilePrefix="config/mydomain/logs/"
XMLRegistry="Xerces JAXP">
...
</Server>
An XMLRegistry-tag is created:
<XMLRegistry
DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
Name="Xerces JAXP"
SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl"
TransformerFactory="weblogic.apache.xalan.processor.TransformerFactoryImpl"
WhenToCache="cache-on-reference"/>
----- Original Message -----
From: "Kher, Amol" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, July 13, 2001 3:15 PM
Subject: RE: Apache SOAP deployed on BEA WL 6.1 Beta Problem
> I have heard of this error and I dont think its related to BEA. Just check
> the troubleshooting guide or FAQ. Mostly its either a classpath
> issue(xerces.jar needs to be the FIRST jar) or XERCES issue (wrong xerces
> version which is less likely since you already have tried it with Tomcat).
>
> regards,
> Amol
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, July 13, 2001 1:03 PM
> To: [EMAIL PROTECTED]
> Subject: Apache SOAP deployed on BEA WL 6.1 Beta Problem
>
>
> I'm having an issue with Apache SOAP 2.2 deployed onto WebLogic 6.1 beta.
> I've deployed it was a web application per the installation docs provided
> by Apache. I can get to all the links and deploy services via browser. I
> can't do it through the command line, I get an error that makes no sense
to
> me:
>
> Ouch, the call failed:
> Fault Code = SOAP-ENV:Client
> Fault String = Unable to resolve namespace URI for 'ns2'.
>
> I can deploy this same service on Tomcat or apache with no problems with
> the same deployment descriptor. Has anyone faced this issue?
>
> As said before I can deploy the service through the browser client, but
> calls to the web service do not work (which they do on Tomcat/Apache).
I'm
> assuming these problems are related and was hoping someone could help me
> out. Thanks again.
>
>
> Eric Miles
>
>
> This message is for the designated recipient only and may contain
> privileged or confidential information. If you have received it in error,
> please notify the sender immediately and delete the original. Any other
> use of the email by you is prohibited.
>
