[AXISCPP-775] When input message element name and the operation name can differ in the WSDL, service not allows operation to invoke.

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.6 Alpha
• Fix Version/s: 1.6 Alpha
• Component/s: Server - Engine
• Environment: All
• Assignee: Don Samisa Abeysinghe
• Reporter: Chinthana Dinapala
• Created: 03/Aug/05 13:34
• Updated: 05/Aug/05 13:06
• Resolved: 05/Aug/05 13:06

Description

Hi All,
I was able to come up with a quick fix to drop the SOAP Action usage on the server side.

However, this morning, testing with the server, I realized that there is a problem in the fix provided. When picking the operation to invoke based on the request SOAP message, it is possible that the SOAP request element name to be different from the operation name. (In other words the input message element name and the operation name can differ in the WSDL)

Looking into the generated Java code for WSDLs, it looks that in Java, the wsdd keeps track of Request and Response element names and map that to the operation name.
We only have the allowed operation name list as of now in our WSDD. What I propose is that we also include the request, response tag name mapping against the operation name in WSDD and we can auto generate this stuff from WSSL tool.

Any thoughts on this are welcome.

Until this is fixed, we will have some tests failing with C++ server side.

Thanks,
Samisa...

Issue Links

• incorporates: AXISCPP-773 Eliminate the SOAPAction HTTP header being mandatory on server side to locate the method
• is related to: AXISCPP-781 Document new changes to server.wsdd syntax to help handle operation to request mapping
• relates to: AXISCPP-603 Setting the SOAPAction for the clients to test with C++ server