axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pasula, Venugopal (Consultant)" <Venugopal.Pas...@GTECH.COM>
Subject xmlns attribute is missing..
Date Wed, 01 Sep 2004 18:53:58 GMT
  I have a problem in verifying the digital signature. one of my Client is
doing digital signature to whole SoapBody. when he is doing the digital
signature, that SoapBody consist an attribute of
"xmlns:ns1="" in all the elements.
and he is passing that sigatre value along with SOAP request. when I
recieved the SoapEnvelope from messagecontext, that xmlns attribute is
missing in all the elements. so my verification is failing. both of we are
using same version of axis (1.1). can u please tell me why that attribute is
missing?? is it a problem with serialization??

here I am listing those 2 soap envelope. please have a look at it.

soapBody at client's place

  <ns1:Body xmlns:ns1="">
 <ns2:execute ns1:encodingStyle=""
  <in0 xsi:type="xsd:string"
  <in1 xsi:type="soapenc:Array" soapenc:arrayType="ns3:NameValuePair[21]"
    <name xsi:type="xsd:string"
    <value xsi:type="xsd:string"
    <name xsi:type="xsd:string"
    <value xsi:type="xsd:string"

soapBody when I get it from messagecontext

  <execute soapenv:encodingStyle=""
   <in0 xsi:type="xsd:string">Lotto6/49</in0>
   <in1 xsi:type="soapenc:Array" soapenc:arrayType="ns2:NameValuePair[21]"
     <name xsi:type="xsd:string">addonNumber</name>
     <value xsi:type="xsd:string">1862116:862116</value>
     <name xsi:type="xsd:string">addonProduct</name>
     <value xsi:type="xsd:string">Spiel77:Super6</value>
     <name xsi:type="xsd:string">address</name>
     <value xsi:type="xsd:string"></value>


-----Original Message-----
From: []
Sent: Wednesday, September 01, 2004 2:42 PM
Subject: [jira] Updated: (AXIS-1488) xs:list itemTypes are forced into
namespace {}

The following issue has been updated:

    Updater: Steve Green (
       Date: Wed, 1 Sep 2004 11:40 AM
New patch, but with unified context.
             Attachment changed to 1488.patch
For a full history of the issue, see:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1488
    Summary: xs:list itemTypes are forced into namespace
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis
             WSDL processing

   Reporter: Steve Green

    Created: Tue, 3 Aug 2004 1:51 PM
    Updated: Wed, 1 Sep 2004 11:40 AM

Generated code from xs:list items uses the wrong namespace for the list.
Attached is some wsdl that demonstrates the problem.  newEntryIDs is class
ModifyResponseType gets generated like this:

    org.w3.www._2001.XMLSchema.IDReferenceType[] newEntryIDs;

The reason for this is in SchemaUtils.getListItemType().  The code in
question finds the array type, throws away any namespace prefix, and returns
a QName in org.w3.www._2001.XMLSchema.

    return new QName(Constants.URI_2001_SCHEMA_XSD, type + "[]");

Also attached is a patch that partially fixes the problem.  The patch will
attempt to find the QName of the base type for the array.  I call this a
partial fix because my patch does not throw an exception if the list item
type cannot be found in the symbol table.  I also suspect that there might
be a better way to solve the problem.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

This email may contain confidential and privileged material for the sole
use of the intended recipient(s). Any review, use, retention, distribution
or disclosure by others is strictly prohibited. If you are not the intended
recipient (or authorized to receive for the recipient), please contact the
sender by reply email and delete all copies of this message. Also, email is
susceptible to data corruption, interception, tampering, unauthorized
amendment and viruses. We only send and receive emails on the basis that we
are not liable for any such corruption, interception, tampering, amendment
or viruses or any consequence thereof.

View raw message