I can confirm that Axis 1.2RC3 has this problem.

Oliver

******************************************************************
�Zurich� Financial Services
Global IT, Shared ASP Europe, UKISA,  Asia / Pacific
Business Application Management Switzerland
CHKIEAMI - Application Integration
OPTA - PST A616
Talackerstrasse 1
CH-8152 Opfikon-Glattbrugg

Phone: +41- 1 628 58 07
Fax: +41 - 1 623 58 07
E-Mail: [EMAIL PROTECTED]



                                                                       
                      "Davanum Srinivas                                
                      (JIRA)"                  An:       [email protected]
                      <[EMAIL PROTECTED]        Kopie:                  
                      he.org>                  Thema:    [jira] Commented: 
(AXIS-1947) possible bug in Axis 1.2.x related to
                                                document/literal       
                      23.04.2005 01:01                                 
                      Bitte antworten                                  
                      an axis-dev                                      
                                                                       
                                                                       




     [
     http://issues.apache.org/jira/browse/AXIS-1947?page=comments#action_63543
      ]

Davanum Srinivas commented on AXIS-1947:
----------------------------------------

Please upload the complete WSDL.

thanks,
dims

> possible bug in Axis 1.2.x related to document/literal
> ------------------------------------------------------
>
>          Key: AXIS-1947
>          URL: http://issues.apache.org/jira/browse/AXIS-1947
>      Project: Axis
>         Type: Bug
>     Reporter: Bo Wang
>     Assignee: Davanum Srinivas

>
> here's the situation: for an operation with doc/literal style and with NO
input message part,
>     <message name="request_reference"/>
>     <message name="return_reference">
>         <part element="tns:reference_wrapper" name="the_reference"/>
>     </message>
>     <portType name="Factory">
>         <operation name="retrieve_reference">
>             <input message="tns:request_reference"
name="retrieve_referenceRequest"/>
>             <output message="tns:return_reference"
name="retrieve_referenceResponse"/>
>         </operation>
>     </portType>
>     <binding name="Factory_SOAPBinding" type="tns:Factory">
>         <soap:binding style="document" transport="
http://schemas.xmlsoap.org/soap/http"/>
>         <operation name="retrieve_reference">
>             <soap:operation soapAction="" style="document"/>
>             <input name="retrieve_referenceRequest">
>                 <soap:body use="literal"/>
>             </input>
>             <output name="retrieve_referenceResponse">
>                 <soap:body use="literal"/>
>             </output>
>         </operation>
>     </binding>
> Axis sends the following message with an empty operation in soap body.
> <soapenv:Envelope xmlns:soapenv="
http://schemas.xmlsoap.org/soap/envelope/"; xmlns:xsd="
http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
>     <soapenv:Body>
>         <retrieve_reference xmlns="
http://www.iona.com/hello_world_soap_http"/>
>     </soapenv:Body>
> </soapenv:Envelope>
> but the following is the soap message with an empty soap body:
> <?xml version='1.0' encoding='utf-8'?>
> <SOAP-ENV:Envelope xmlns:xs="http://www.w3.org/2001/XMLSchema";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>
>     <SOAP-ENV:Body></SOAP-ENV:Body>
> </SOAP-ENV:Envelope>
> this happens in axis 1.2 beta, rc1, rc2, and rc3. (java version)
> I think it's a bug, isn't it?

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira









   ******************* BITTE BEACHTEN *******************
   Diese Nachricht (wie auch allf�llige Anh�nge dazu) beinhaltet
   m�glicherweise vertrauliche oder gesetzlich gesch�tzte Daten oder
   Informationen. Zum Empfang derselben ist (sind) ausschliesslich die
   genannte(n) Person(en) bestimmt. Falls Sie diese Nachricht
   irrt�mlicherweise erreicht hat, sind Sie h�flich gebeten, diese unter
   Ausschluss jeder Reproduktion zu zerst�ren und die absendende Person
   umgehend zu benachrichtigen. Vielen Dank f�r Ihre Hilfe.

Reply via email to