Fixed me too! Tnx Stefan.
For those who repeat this fix:
1) Remember to add xerces to start of WL
classpath.
2) Using WL console (rather than editing
config.xml):
a)
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]
b) mydomain/Servers/myserver -> “Services”
tab / ”XML” tab
�������������� Select “Xerces JAPX”
from “XML Registry” pulldown
My resulting config.xml entries:
<Server ListenPort="7001"
�����������
Name="myserver"
�����������
NativeIOEnabled="true"
�������
����TransactionLogFilePrefix="config/mydomain/logs/"
�����������
XMLRegistry="Xerces JAXP">
<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"/>
�
This works for me …
NT/soap2.2/xerces1.4.0/WL6.1beta
Steve
-----Original Message-----
From: Ed Keen
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 13, 2001 7:26 AM
To: '[EMAIL PROTECTED]'
Subject: RE: compatibility with
weblogic 6.1 beta
That fixed it!
Thanks, Stefan!
-----Original Message-----
From: Stefan Dube
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 13, 2001
4:15 AM
To: [EMAIL PROTECTED]
Subject: RE: compatibility with
weblogic 6.1 beta
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
>
Hope that helps,
-sd
> -----Original Message-----
> From: Erik Onnen [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, June 13, 2001
1:33 AM
> To: '[EMAIL PROTECTED]
'
> Subject: RE: compatibility
with weblogic 6.1 beta
>
>
> The "unable to resolve
namespace" problem is because BEA in
> their infinite
> wisdom chose to mesh Xerces
into their own libraries.
> Unfortunately they
> used an old version and
because it is so embedded, you can't
> just replace a
> JAR. I was able to get 2.1
working on 6.0 sp1 by moving
> Xerces to the front
> of the classpath in the
startup script. Ed, when WL won't
> start, what is the
> error you get? I haven't heard
of that happening before.
> Steve, when you say
> Xerces is in your classpath,
is it at the front, before weblogic.jar?
>
> -----Original Message-----
> From: Steve Livingston
> To: [EMAIL PROTECTED]
> Sent: 6/12/01 6:46 PM
> Subject: RE: compatibility
with weblogic 6.1 beta
>
> 1) I get the same error (with
NT, soap-2.2 and wl-6.1beta) and have
> found no solution:
>
>
E:\apache\soap-2_2\samples\addressbook>java
>
org.apache.soap.server.ServiceManagerClient
> http://slivings:7001/soap/servlet/rpcrouter
list
> Deployed Services:
>
>
E:\apache\soap-2_2\samples\addressbook>java
>
org.apache.soap.server.ServiceManagerClient
> http://slivings:7001/soap/servlet/rpcrouter
deploy dd.xml
> Ouch, the call failed:
> Fault
Code = SOAP-ENV:Client
> Fault String =
Unable to resolve namespace URI for 'ns2'.
>
> 2) My wl-6.1b will start with
xerces in classpath, but same error
> occurs.
>
> Can anyone help?
>
> Steve
>
>
> -----Original Message-----
> From: Ed Keen [mailto:[EMAIL PROTECTED]]
> Sent: Monday, June 11, 2001
6:36 PM
> To: '[EMAIL PROTECTED]'
> Subject: compatibility with
weblogic 6.1 beta
>
> Has anyone gotten Apache soap
version 2.2 to work with Weblogic 6.1
> beta?
> There seems to be a xerces
incompatibility. The weblogic.jar file
> contains
> the xerces library. If
you put xerces.jar first in the classpath,
> weblogic
> won't even start.
However, if you put weblogic.jar first in the
> classpath,
> you get this error when
attempting to deploy services using the
> ServiceManagerClient:
"Unable to resolve namespace URI for 'ns2.'"
>
> This obviously seems to be a
xerces parsing issue. Does
> anyone know of
> a
> workaround for this?
>
> Thanks,
> Ed
