You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Lisa Penninger (JIRA)" <ji...@apache.org> on 2009/04/10 20:49:14 UTC

[jira] Created: (AXIS2-4307) missing xsi:type when operation element has abstract type

missing xsi:type when operation element has abstract type
---------------------------------------------------------

                 Key: AXIS2-4307
                 URL: https://issues.apache.org/jira/browse/AXIS2-4307
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
    Affects Versions: 1.4
            Reporter: Lisa Penninger
         Attachments: tiny.wsdl

When using an operation element whose type is abstract, the xsi:type declaration for the actual concrete type is missing in the generated XML.  The generated XML is:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Body>
    <copy xmlns="http://www.strongmail.com/services">
      <fromId><id>123</id></fromId>
      <newName>New Name</newName>
    </copy>
  </soapenv:Body>
</soapenv:Envelope>

However, what is expected is:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
  <soapenv:Body>
    <copy xmlns="http://www.strongmail.com/services" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="TargetCopyRequest">
      <fromId><id>123</id></fromId>
      <newName>New Name</newName>
    </copy>
  </soap:Body>
</soap:Envelope>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (AXIS2-4307) missing xsi:type when operation element has abstract type

Posted by "Lisa Penninger (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12697923#action_12697923 ] 

Lisa Penninger commented on AXIS2-4307:
---------------------------------------

Forgot to mention this is with jaxbri binding.

> missing xsi:type when operation element has abstract type
> ---------------------------------------------------------
>
>                 Key: AXIS2-4307
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4307
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.4
>            Reporter: Lisa Penninger
>         Attachments: tiny.wsdl
>
>
> When using an operation element whose type is abstract, the xsi:type declaration for the actual concrete type is missing in the generated XML.  The generated XML is:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>   <soapenv:Body>
>     <copy xmlns="http://www.strongmail.com/services">
>       <fromId><id>123</id></fromId>
>       <newName>New Name</newName>
>     </copy>
>   </soapenv:Body>
> </soapenv:Envelope>
> However, what is expected is:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>   <soapenv:Body>
>     <copy xmlns="http://www.strongmail.com/services" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="TargetCopyRequest">
>       <fromId><id>123</id></fromId>
>       <newName>New Name</newName>
>     </copy>
>   </soap:Body>
> </soap:Envelope>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (AXIS2-4307) missing xsi:type when operation element has abstract type

Posted by "Lisa Penninger (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lisa Penninger updated AXIS2-4307:
----------------------------------

    Attachment: tiny.wsdl

Test wsdl for the bug report

> missing xsi:type when operation element has abstract type
> ---------------------------------------------------------
>
>                 Key: AXIS2-4307
>                 URL: https://issues.apache.org/jira/browse/AXIS2-4307
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>    Affects Versions: 1.4
>            Reporter: Lisa Penninger
>         Attachments: tiny.wsdl
>
>
> When using an operation element whose type is abstract, the xsi:type declaration for the actual concrete type is missing in the generated XML.  The generated XML is:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>   <soapenv:Body>
>     <copy xmlns="http://www.strongmail.com/services">
>       <fromId><id>123</id></fromId>
>       <newName>New Name</newName>
>     </copy>
>   </soapenv:Body>
> </soapenv:Envelope>
> However, what is expected is:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>   <soapenv:Body>
>     <copy xmlns="http://www.strongmail.com/services" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="TargetCopyRequest">
>       <fromId><id>123</id></fromId>
>       <newName>New Name</newName>
>     </copy>
>   </soap:Body>
> </soap:Envelope>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.