[jbossws-issues] [JBoss JIRA] Updated: (JBWS-1933) Use of xsi:type on the types with rpc/encoded

[Heiko Braun (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBWS-1933?page=all ]

Heiko Braun updated JBWS-1933:
------------------------------

    Fix Version/s: jbossws-native-2.0.4
                       (was:  jbossws-native-2.0.3)

> Use of xsi:type on the types with rpc/encoded
> ---------------------------------------------
>
>                 Key: JBWS-1933
>                 URL: http://jira.jboss.com/jira/browse/JBWS-1933
>             Project: JBoss Web Services
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: jbossws-jaxrpc
>    Affects Versions:  jbossws-2.0.2
>            Reporter: Darran Lofthouse
>         Assigned To: Darran Lofthouse
>             Fix For: jbossws-native-2.0.4
>
>
> The following describes how RPC/Encoded types should be identified: -
> For each element containing a value, the type of the value MUST be represented by at least one of the following conditions:
> (a) the containing element instance contains an xsi:type attribute,
> (b) the containing element instance is itself contained within an element containing a (possibly defaulted) SOAP-ENC:arrayType attribute or
> (c) or the name of the element bears a definite relation to the type, that type then determinable from a schema. 
> JBossWS does not currently use the xsi:type on the types so stacks such as Axis are unable to identify the type inside the element which represents the operation name.

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