RE: xs:anyType deserialize problem in Axis2 version 1.2

[mailto:[EMAIL PROTECTED] Sent: Friday, August 03, 2007 12:09 AM To: axis-user@ws.apache.org Subject: Re: xs:anyType deserialize problem in Axis2 version 1.2 Ken Tam wrote: Hi all, I've exposed a POJO web service with a method which returns another POJO containing a member of type Object

xs:anyType deserialize problem in Axis2 version 1.2

Hi all, I've exposed a POJO web service with a method which returns another POJO containing a member of type Object. This translates to xs:anyType in the WSDL. I wrote an AXIS2 client to consume this web service. The value of the Object is null after the deserialization process. The actual value

WSS4J and WS-Security 1.1

Hi all, The WSS4J website mentioned support for WS-Security 1.0. Does it support 1.1? If not, what alternatives are there? Thanks, Ken

Encountered wrong key usage exception with WSS4J/Axis 1.4

Hi all, I was able to use the x509.pfx.msft sample key file included with the WSS4J download to encrypt a SOAP request. However, I got the Wrong key usage exception when using a different PFX file exported from IE (both public/private keys were exported). Is there something special about the

WS Security with Axis 1.4

Hi all, I am using Axis 1.4 on a standalone Java client to invoke a web service. This is working fine but the same web service has enabled WSE 3.0 security. I have the client and server certificates. How do I apply WS Security? Is WSS4J the right way to go? Any sample code would be helpful.

RE: Schema validation

in confidentialinformation intended only for the person(s) to whom this email message isaddressed.If you have received this email message in error, please notify the sender immediately by telephone or email and destroy the originalmessage without making a copy.Thank you.---

Schema validation

Hi all, I am consuming web services made available from my customer. I was given a very elaborate WSDL with schemas and I was able to generate the stubs by using Axis's WSDL2Java. Everything was working fine until the service was changed on the customer's end. This causes the deserialization step

RE: passing XML document as input parameter

Hi all, There are quite a few postings on this topic. Another (preferred) alternative is to pass XML as an attachment. Regards, Ken -Original Message-From: Suavi Ali Demir [mailto:[EMAIL PROTECTED]Sent: Wednesday, May 17, 2006 10:45 AMTo: axis-user@ws.apache.orgSubject: