Missing prefix for mustunderstand

Hi, I am createing some header elements but I see that the namespeacr prefix for mustunderstand and actor attributes for these header elements is missing. I am pasting below part of the xml genereated. You can see the namespace prefix is missing. Can anyone help me on this? ?xml

deserializer exception with Axis 1.4

Hi, I am working with Axis 1.4. I am using ws-addressing mode on my soap-server which uses Axis 1.4. The body of request sent by the server (to the server denoted by reply to tag) looks as below. What can be the reason for the exception? soapenv:Body processIPDRDocResponse

Migrate from Axis 1.1 to Axis 1.4

Hi, We have migrated from Axis 1.1 to Axis 1.4 and I see for the code generated by WSDL2JAVA is quite different than that was generated by 1.1. Is there any way to preserve backward compacitibilty. Thanks Shripad This message and the information contained herein is proprietary

WS-Addressing Migrate from Axis 1.1 to Axis 1.4

Hi, We have migrated from Axis 1.1 to Axis 1.4. In case of such migration , is there any additional thing which needs to be taken care of if we are working with WS-Addressing mode. Thanks Shripad This message and the information contained herein is proprietary and

WSDoAllReceiver: security processing failed (actions mismatch)

I am getting following error. What can be the reason for this? faultstringWSDoAllReceiver: security processing failed (actions mismatch)/faultstring I am sending following header as part of request. soapenv:Header wsse:Security soapenv:mustUnderstand=1

RE: Username token implemetation

secureEnvelope = Util.createSoapEnvelopeFromDOM(soapDocument); messageContext.setEnvelope(secureEnvelope); regards robert 2008/7/31 Shripad Gokhale [EMAIL PROTECTED] Hi, I am trying to implement user name token with Axis 1.4 and WSS4J on server side. Where can I get a good reference material

Code generation problem

Hi, The code generated by AXIS in our software gets compilation errors when using a complex WSDL that includes other XSDs. The attached MessageInterfaces.zip file contains the xsdl file at MessageInterfaces\wsdl\billingServices\v3.3\GetProfile.wsdl. This file contain references to other xsd

RE: Code generation problem

The attachements can ne found below https://issues.apache.org/jira/browse/AXIS-2755 From: Shripad Gokhale [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 30, 2008 11:46 AM To: axis-user@ws.apache.org Subject: Code generation problem Hi, The code generated by AXIS in our

Code Generation Problem ( Order of constructor parameters)

In a certain situation, the code generated by AXIS 1.4 is giving compilation errors. After investigation, I found that in some classes, the super class's constructors were called with wrong order of input parameters. For example, a class CustomerListEntity which extends ListMessageEntity calls

Username token implemetation

Hi, I am trying to implement user name token with Axis 1.4 and WSS4J on server side. Where can I get a good reference material or tutorial about the changes that are required? Some of the links I found of google provide only partial information. Thanks Shripad This message and the

upgrade from axis 1 to axis 2 ?

Hi, Is it possible to upgrade straight away from axis 1 to axis 2 on a SOAP Server? Or are there any complications involved? Thanks Shripad This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at

Using WSS4J with Axis 1.4

Hi, I have developed a soap server using axis 1.4 in core java. Now I want to add security support using ws4j. What are the changes I need to do in order to achieve this? Thanks Shripad This message and the information contained herein is proprietary and confidential and subject to the

Interoperability in axis 1.4 and wse 3.0

Hi, I am using axis 1.4 currently in my application. I want to know if it is compactible with web services extension 3.0 (wse 3.0). Where can I get this information? Thanks Shripad This message and the information contained herein is proprietary and confidential and subject to the