[jira] Resolved: (AXIS-390) RPCElement serialization doesn't use prefixes

["Davanum Srinivas (JIRA)" <ax...@ws.apache.org>]

     [ http://issues.apache.org/jira/browse/AXIS-390?page=all ]
     
Davanum Srinivas resolved AXIS-390:
-----------------------------------

     Assign To:     (was: Axis Developers Mailing List)
    Resolution: Fixed

i think this is already fixed.

-- dims

> RPCElement serialization doesn't use prefixes
> ---------------------------------------------
>
>          Key: AXIS-390
>          URL: http://issues.apache.org/jira/browse/AXIS-390
>      Project: Axis
>         Type: Bug
>   Components: Serialization/Deserialization
>     Versions: 1.0-rc1
>  Environment: Operating System: Other
> Platform: Other
>     Reporter: Dirk Wollscheid

>
> The code in RPCElement.outputImpl creates a default namespace when using RPC/literal encoding. This means that all elements in message parts that have previously ment to unqualified are now in that default namespace. 
> I suggest to avoid that
> a) the user can set a prefix on RPCElement with setPrefix
> b) the outputImpl code is change to not add a default namespace when this prefix is set. E.g. the code will be change to this:
>        if (isRPC || noParams) {
>             // Set default namespace if appropriate (to avoid prefix mappings
>             // in literal style).  Do this only if there is no encodingStyle.
>             if (encodingStyle != null && encodingStyle.equals("") && getPrefix()==null) {
>                 context.registerPrefixForURI("", getNamespaceURI());
>             }
>             context.startElement(new QName(namespaceURI,name), attributes);
>         }
>         for (int i = 0; i < params.size(); i++) {
>             RPCParam param = (RPCParam)params.elementAt(i);
>             if (!isRPC && encodingStyle.equals("") && getPrefix()==null) {
>                 context.registerPrefixForURI("", param.getQName().getNamespaceURI());
>             }
>             param.serialize(context);
>         }

-- 
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