You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by "Alex Boisvert (JIRA)" <ji...@apache.org> on 2007/04/18 16:53:15 UTC

[jira] Created: (ODE-110) Complex type wrapper element is visible in messages sent by the engine

Complex type wrapper element is visible in messages sent by the engine
----------------------------------------------------------------------

                 Key: ODE-110
                 URL: https://issues.apache.org/jira/browse/ODE-110
             Project: Ode
          Issue Type: Bug
          Components: BPEL Runtime
            Reporter: Alex Boisvert
         Assigned To: Maciej Szefler


Apparently, the complex type wrapper element <xsd-complex-type-wrapper/> is visible in message sent by the engine.

In this case, we have a message definition:

<message name="createTaskRequest">
  <part name="wipart" type="tns:StringArray"/>
</message>

with complex type:

<complexType name="StringArray">
  <sequence>
    <element name="item" type="xsd:string" minOccurs="0" maxOccurs="unbounded" />
  </sequence>
</complexType>

leading to this response:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
    <soapenv:Header/>
    <soapenv:Body>
        <axis2ns8:testItResponse xmlns:axis2ns8="http://ode/bpel/unit-test.wsdl">
            <wipart>
                <xsd-complex-type-wrapper>      <!-- ????? --->
                    <tm:item xmlns:tm="urn:TaskManager">test1text</tm:item>
                    <tm:item xmlns:tm="urn:TaskManager">test2text</tm:item>
                </xsd-complex-type-wrapper>     <!-- ????? --->
            </wipart>
        </axis2ns8:testItResponse>
    </soapenv:Body>
</soapenv:Envelope>


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


[jira] Commented: (ODE-110) Complex type wrapper element is visible in messages sent by the engine

Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/ODE-110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12489782 ] 

Alex Boisvert commented on ODE-110:
-----------------------------------

This relates to the following ode-user message thread:
http://mail-archives.apache.org/mod_mbox/incubator-ode-user/200704.mbox/%3c20070417170317.w89y5sqagcgwwsgw@horde.fambos.nl%3e

> Complex type wrapper element is visible in messages sent by the engine
> ----------------------------------------------------------------------
>
>                 Key: ODE-110
>                 URL: https://issues.apache.org/jira/browse/ODE-110
>             Project: Ode
>          Issue Type: Bug
>          Components: BPEL Runtime
>            Reporter: Alex Boisvert
>         Assigned To: Maciej Szefler
>         Attachments: request.soap, TaskManagerTest.zip
>
>
> Apparently, the complex type wrapper element <xsd-complex-type-wrapper/> is visible in message sent by the engine.
> In this case, we have a message definition:
> <message name="createTaskRequest">
>   <part name="wipart" type="tns:StringArray"/>
> </message>
> with complex type:
> <complexType name="StringArray">
>   <sequence>
>     <element name="item" type="xsd:string" minOccurs="0" maxOccurs="unbounded" />
>   </sequence>
> </complexType>
> leading to this response:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>     <soapenv:Header/>
>     <soapenv:Body>
>         <axis2ns8:testItResponse xmlns:axis2ns8="http://ode/bpel/unit-test.wsdl">
>             <wipart>
>                 <xsd-complex-type-wrapper>      <!-- ????? --->
>                     <tm:item xmlns:tm="urn:TaskManager">test1text</tm:item>
>                     <tm:item xmlns:tm="urn:TaskManager">test2text</tm:item>
>                 </xsd-complex-type-wrapper>     <!-- ????? --->
>             </wipart>
>         </axis2ns8:testItResponse>
>     </soapenv:Body>
> </soapenv:Envelope>

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


[jira] Updated: (ODE-110) Complex type wrapper element is visible in messages sent by the engine

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

Alex Boisvert updated ODE-110:
------------------------------

    Attachment: request.soap
                TaskManagerTest.zip

> Complex type wrapper element is visible in messages sent by the engine
> ----------------------------------------------------------------------
>
>                 Key: ODE-110
>                 URL: https://issues.apache.org/jira/browse/ODE-110
>             Project: Ode
>          Issue Type: Bug
>          Components: BPEL Runtime
>            Reporter: Alex Boisvert
>         Assigned To: Maciej Szefler
>         Attachments: request.soap, TaskManagerTest.zip
>
>
> Apparently, the complex type wrapper element <xsd-complex-type-wrapper/> is visible in message sent by the engine.
> In this case, we have a message definition:
> <message name="createTaskRequest">
>   <part name="wipart" type="tns:StringArray"/>
> </message>
> with complex type:
> <complexType name="StringArray">
>   <sequence>
>     <element name="item" type="xsd:string" minOccurs="0" maxOccurs="unbounded" />
>   </sequence>
> </complexType>
> leading to this response:
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
>     <soapenv:Header/>
>     <soapenv:Body>
>         <axis2ns8:testItResponse xmlns:axis2ns8="http://ode/bpel/unit-test.wsdl">
>             <wipart>
>                 <xsd-complex-type-wrapper>      <!-- ????? --->
>                     <tm:item xmlns:tm="urn:TaskManager">test1text</tm:item>
>                     <tm:item xmlns:tm="urn:TaskManager">test2text</tm:item>
>                 </xsd-complex-type-wrapper>     <!-- ????? --->
>             </wipart>
>         </axis2ns8:testItResponse>
>     </soapenv:Body>
> </soapenv:Envelope>

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