Hi Axis users and developers,

I'm facing a very = unique issue and any help, suggestion pointers to resolve this would be highly appreciated.

Context of the = issue

----------------------------

I have 6 operations = (web services) in one WSDL. All these web services are deployed as = Axis-Message style services. All of these web services takes Document as input and = returns the document. Following are the method signatures I have for these web = services.

1. public Document = createProfile(Document body);

2. public Document = updateProfile(Document body);

3. public Document = retrieveProfile(Document body);

4. public Document = retrieveTemplate(Document body);

5. public Document = retrieveTemplateAndProfile(Document body);

Here is the = server-config.wsdd file excerpts for these services.

<parameter = qname=3D"pns:createProfile" xmlns:pns=3D"http://eprofile.globalops.hp.com/eProfileService" type=3D"tns:Document" = xmlns:tns=3D"http://xml.apache.org/xml-soap"/>=

= </operation>

<parameter = qname=3D"pns:updateProfile" xmlns:pns=3D"http://eprofile.globalops.hp.com/eProfileService" type=3D"tns:Document" = xmlns:tns=3D"http://xml.apache.org/xml-soap"/>=

= </operation>

<parameter = qname=3D"pns:retrieveProfile" xmlns:pns=3D"http://eprofile.globalops.hp.com/eProfileService" type=3D"tns:Document" = xmlns:tns=3D"http://xml.apache.org/xml-soap"/>=

= </operation>

<parameter = qname=3D"pns:retrieveTemplate" xmlns:pns=3D"http://eprofile.globalops.hp.com/eProfileService" type=3D"tns:Document" = xmlns:tns=3D"http://xml.apache.org/xml-soap"/>=

= </operation>

<parameter = qname=3D"pns:ApplicationTemplateChecksum" xmlns:pns=3D"http://eprofile.globalops.hp.com/eProfileService" type=3D"tns:Document" = xmlns:tns=3D"http://xml.apache.org/xml-soap"/>=

= </operation>

<parameter = qname=3D"pns:checkTemplate" xmlns:pns=3D"http://eprofile.globalops.hp.com/eProfileService" type=3D"tns:Document" = xmlns:tns=3D"http://xml.apache.org/xml-soap"/>=

= </operation>

= </service>

Problem = Statement

---------------------------

My problem is, if I = use the axis client then I'm not able to invoke the intended operation. As per = WSDL 1.1 specification section #3.5, the request for doc lit the input data is = wrapped in the message-part name element and it appears in the body of the = request. If I do this, then I'm able to invoke the intended operation. But the Axis = Client does not wrap the input in message-part name element. Any = help/suggestions in resolving the following issues are much appreciated.

1. How can I make = my DII client to invoke the intended operation? 2. Why Axis does not follow the = WSDL 1.1 specification section #3.5 and wraps the input in message part name = (see the sample request by Axis and the correct request which is able to = invoke the service, at the end of this email) 3. Is there any workaround, other = than specifying each operation in a separate WSDL and deploy those as = different endpoint. i.e. one operation one WSDL, one operation each endpoint. 4. Specifying the SOAPAction for operation does not work in Axis, Looks = like this is and Axis limitation. I even saw the excerpts of the Axis source code = posted by one of the user, which does not handle the SOAPAction. What are my = other alternatives.

Here is the sample = request which can invoke the intended operation.

<?xml version=3D"1.0" = encoding=3D"UTF-8"?>

<SOAP-ENV:Envelope = xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" = xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance">

<SOAP-ENV:Header><ns1:eProfileHeader xmlns:ns1=3D"http://eprofile.globalops.hp.com/eProfileService"&= gt;<ApplicationID>AppID</ApplicationID><LanguageCode>La= ngID</LanguageCode><HPPID>HppID</HPPID><SiteMinderSI= D>SID</SiteMinderSID><TemplateID>DummyTemplateID</Templ= ateID></ns1:eProfileHeader> </SOAP-ENV:Header> <SOAP-ENV:Body>

= <checkTemplate xmlns=3D"http://eprofile.globalops.hp.com/eProfileService">&= lt;ApplicationTemplateChecksum>

= <TemplateChecksum>2003-11-14T16:44:50.633Z</TemplateChecksum>=

</ApplicationTemplateChecksum></checkTemplate>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Here is how the = request generated by Axis client, which fails to invoke the intended = operation

<?xml version=3D"1.0" = encoding=3D"UTF-8"?>

<SOAP-ENV:Envelope = xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" = xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance">

= <ApplicationTemplateChecksum>

= <TemplateChecksum>2003-11-14T16:44:50.633Z</TemplateChecksum>=

</ApplicationTemplateChecksum>

</SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Any way, either by = modifying the WSDD, or any change on the client side, or any other possible way by = which I can invoke the intended operation of message style, where the multiple operations are served by single endpoint location.

Thanks in = advance.

Shrikant = Wagh

HPP/eProfile QA = Lead