RE: WSDL changes.

[Kellogg, Richard]

Title: Interoperability Issue??

Check out the "Securing an Axis-based Web Service" (security.html) in the most recent releases (1.1 RC1 or 1.1 RC2).  I am not sure if it existed before those.

 

-----Original Message-----
From: Ghershony, Arie [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 2:58 PM
To: '[EMAIL PROTECTED]'
Subject: RE: WSDL changes.

which document?

-----Original Message-----
From: Kellogg, Richard [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 2:02 PM
To: [EMAIL PROTECTED]
Subject: RE: WSDL changes.

Review the "Securing Axis" section of the docs.  It tells you how to override the WSDL returned.

 

Take care,

Rick

 

-----Original Message-----
From: Ghershony, Arie [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 1:54 PM
To: '[EMAIL PROTECTED]'
Subject: WSDL changes.

How do I manually change WSDL document that was deployed??

 

Thanks.

[Ghershony, Arie] 

 -----Original Message-----
From: Anecito, Anthony (HQP) [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 06, 2003 1:15 PM
To: '[EMAIL PROTECTED]'
Subject: Interoperability Issue??

Hi All,

I was getting an Axis Fault message (sent back to the client) about serializer not being registered. My research so far indicates that I may need to use SOAPSerializer somehow to create a serializable class. I am using JAX-RPC from Sun for a very specific reason and I have a complex object that gets serialized over to the Axis SOAP server (version 1.0).

Has anyone used SOAPSerializer or know where I can find a working example? So far my searches on Google have yielded no results with working examples.

Is this a Interoperability issue?? I am hoping I do not need to have special Axis jars on the client to eliminate Axis Fault the serialization registration message.

Many Thanks,
Tony