Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <372726625.1106791878791.JavaMail.jira@ajax.apache.org>
Date: Thu, 27 Jan 2005 03:11:18 +0100 (CET)
From: "Bill Keese (JIRA)" <axis-dev@ws.apache.org>
To: axis-dev@ws.apache.org
Subject: [jira] Created: (AXIS-1784) Axis client should not generate xsi:type
 attributes in document/literal or wrapped/literal mode
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

Axis client should not generate xsi:type attributes in document/literal or wrapped/literal mode
-----------------------------------------------------------------------------------------------

         Key: AXIS-1784
         URL: http://issues.apache.org/jira/browse/AXIS-1784
     Project: Axis
        Type: Bug
    Versions: 1.2RC2    
    Reporter: Bill Keese
    Priority: Minor


Axis generates xsi:type=... attribute definitions even in literal mode.  It shouldn't.  The fix should be in SerializationContext:

            sendXSIType = ( msgContext.getOperationUse() == Use.ENCODED );

(or something like that).

Also, ArraySerializer() has the following code which shouldn't be executed except for RPC/Encoded mode:
            if (typeI != -1) {
                attrs.setAttribute(typeI,
                                   schema.getXsiURI(),
                                   "type",
                                   qname,
                                   "CDATA",
                                   context.qName2String(soapArray));
            } else {
                attrs.addAttribute(schema.getXsiURI(),
                                   "type",
                                   qname,
                                   "CDATA",
                                   context.qName2String(soapArray));
            }


Workaround:

In client code, do

     call.setProperty(Call.SEND_TYPE_ATTR, Boolean.FALSE);


-- 
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
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira