>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 ve
HTML file, I'll merge it into the FAQs hosted on the web-site
(and the install docs for WL).
Thanks,
-Matt
-Original Message-
From: Steve Livingston
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 13, 2001 1:10 PM
To: [EMAIL PROTECTED]
Subject: RE: compatibility
t
> 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?
Newsflash: I fell back to WL6.0sp2 and all is well...
I notice that WL6.1beta installs .../bea/jdk131 where WL6.0sp2 installs
.../bea/jsk130. Dunno if this is the source of the problem
Steve
-Original Message-
From: Steve Livingston [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 12
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?
---
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.apach
