Hi ,

I believe the problem is that SOAP 2.2 uses JAXP and WL uses their bundled
xerces as JAXP parser.

     To override this you have to modify the config.xml like this: (or use
the web console)

     Add following element as child of the <Domain> element:

         <XMLRegistry
DocumentBuilderFactory="org.apache.xerces.jaxp.DocumentBuilderFactoryImpl"
           Name="Xerces JAXP"
           SAXParserFactory="org.apache.xerces.jaxp.SAXParserFactoryImpl"
         />

     and modify the <Server> element like this:

         <Server
           InstrumentStackTraceEnabled="true"
           ListenPort="80"
           LogRemoteExceptionsEnabled="true"
           Name="myServer"
           NativeIOEnabled="true"
           XMLRegistry="Xerces JAXP"         <-- only this line is important
         >


Also 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 


HTH
Venkat





-----Original Message-----
From: Radek Wisniewski [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 17, 2001 3:01 AM
To: [EMAIL PROTECTED]
Subject: Deployment problem on Weblogic 6.1


While deploying I become an error:

Ouch, the call failed:
  Fault Code   = SOAP-ENV:Client
  Fault String = Unable to resolve namespace URI for 'ns2'.

It haven't happend on Weblogic 5.1 and Tomcat on Linux so I'm sure my
DeploymentDescriptor.xml is ok.

Any ideas?
Probably 6.1 on classpath use own corrupted JAXP implementation, but why
use it for SOAP webapplication?


Radek Wisniewski

Reply via email to