Thanks for the advice.
Finally figured out the problem. I use JRun server and I didn't add the
right parser file into the global.properties file. The interesting thing is
that even I didn't have the right file before, the server can get the
"Sorry, ..." message for the SOAP RPC Router test.
Yu
hi
does anyone encounter this problem? I am using weblogic 6.1sp1 with apache
soap 2.2. The function of the webservice is very simple as follow
public class testWebService
{
public String getXML (String xml) throws Exception
{
System.out.println("received message");
System.ou
You should find larger problems using xerces 1.3.1 which have been discussed
on this list and possibly even the newest docs. Other versions of xerces
are fine, including 1.2.3, 1.3.0 and 1.4.x.
Scott
- Original Message -
From: "Jean-Yves MENGANT" <[EMAIL PROTECTED]>
To: "Apachesoap" <[E
Title: RE: oracle soap
Bineet,
We
have a set of B2B data exchange services implemented in database (stored
procedures + data). We also have a number of transport interfaces to access
those services (ex. Web-interface, FTP, RMI, ..., SOAP). SOAP is just one of
them. It allows our clients to
Hi ,
Not sure if this problem has already been reported , I did not see
it looking through the mail list archive ,
Using the soap 2.2
how to reproduce it :
use xerces 1.3.1 as xml parser.
use the sample TestProvider class.
unregister the "hello" service if registered.
( in order to gen
I feel like a broken record repeating this advice...
> > > Ouch, the call failed:
> > > Fault Code = SOAP-ENV:Server.Exception:
> > > Fault String = java.lang.NoSuchMethodError
One possible cause - the JVM is finding an earlier XML parser
that does not support namespaces before it finds t
