I'm been using Apache SOAP 2.2 with Tomcat 3.2.3.
I recently upgraded to Tomcat 4.0.1 and my SOAP
message-style services have stopped working. RPC-style
services still work fine, so I'm confident that I'm
installing my jar files in the correct place (ie,
$CATALINA_HOME/lib).
Has anyone else exp
Hi,
I've seen some messages on this issue, but still have some other
questions regarding it.
I use Tomcat 3.2.2 with Apache SOAP 2.2, and, as other people
mentionned, the CLASSPATH used when looking up providing classes seems
to be the classpath that was set when Tomcat was started, NOT includin
Title: BeanSerializer with JDK 1.4
I came across a problem with the other day that I haven't seen documented anywhere. It's not really an Apache SOAP bug, but I can't reproduce it any other way.
I'm using Apache SOAP 2.2, Tomcat 3.2.3, and JDK 1.4.0-beta3.
BeanSerializer fails to deserializ
Hi Mark,
Were you able to fix the problem? If not let me know and we can
try sending you the jar directly.
Sanjiva.
- Original Message -
From: "Mark Swanson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, November 16, 2001 3:41 AM
Subject: WSIF bad jar file.
> Does anyone e
Mark Swanson wrote:
>Does anyone else get this when they `jar xvf wsif-all-1.0.jar` ?
>
>I'm trying to use the IBM WSIF package found:
>http://alphaworks.ibm.com/tech/wsif
>
>Thanks.
>
>extracted: com/ibm/wsif/WSIFStaticPortFactory.class
> created: com/
>java.util.zip.ZipException: invalid store
Hi
In the binding element of WSDL, there is SoapAction attribute in the
operation element.
Now if a Soap Client *IN ANY SOAP IMPLEMENTATION* is written using above
WSDL file , then *is it necessary* that Soap request would always contain
the *SoapActio
This works for me:
params.addElement(new Parameter("foo", Integer.class, new Integer(foo),
null));
Eric
-Original Message-
From: Jeremy Levy [mailto:[EMAIL PROTECTED]]
Sent: Thursday, November 15, 2001 5:29 PM
To: [EMAIL PROTECTED]
Subject: Parameters types
Okay, I am very new to SOA
Hi,
I'm having problems integrating an Apache SOAP client with a number of
SOAP-enabled application servers. The problem is the way Apache SOAP appears
to handle NULL values, in that it attaches the xsi:null="true" attribute to
the appropriate element.
I have looked at http://www.w3.org/TR/SOA
This is some more information on the Weblogic6.1 NullPointerException bug,
reported by Tony Yip (see
http://marc.theaimsgroup.com/?l=soap-user&m=100470865507174&w=2).
I discovered that only an Apache Soap client seems to provoke the exception
on the server. Other clients, like the Borland Soap co
