Return-Path: 
 <axis-c-dev-return-2348-apmail-ws-axis-c-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-c-dev-archive@www.apache.org
Received: (qmail 65154 invoked from network); 12 Oct 2004 15:35:55 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur-2.apache.org with SMTP; 12 Oct 2004 15:35:55 -0000
Received: (qmail 14717 invoked by uid 500); 12 Oct 2004 15:35:55 -0000
Delivered-To: apmail-ws-axis-c-dev-archive@ws.apache.org
Received: (qmail 14677 invoked by uid 500); 12 Oct 2004 15:35:54 -0000
Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:axis-c-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-c-dev-unsubscribe@ws.apache.org>
list-post: <mailto:axis-c-dev@ws.apache.org>
List-Id: "Apache AXIS C Developers List" <axis-c-dev.ws.apache.org>
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Delivered-To: mailing list axis-c-dev@ws.apache.org
Received: (qmail 14662 invoked by uid 99); 12 Oct 2004 15:35:54 -0000
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=NO_REAL_NAME
X-Spam-Check-By: apache.org
Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10)
  by apache.org (qpsmtpd/0.28) with SMTP; Tue, 12 Oct 2004 08:35:53 -0700
Received: (qmail 8028 invoked from network); 12 Oct 2004 15:37:51 -0000
Received: from localhost (HELO nagoya) (127.0.0.1)
  by nagoya.betaversion.org with SMTP; 12 Oct 2004 15:37:51 -0000
Message-ID: <411052464.1097595471186.JavaMail.apache@nagoya>
Date: Tue, 12 Oct 2004 08:37:51 -0700 (PDT)
From: axis-c-dev@ws.apache.org
To: axis-c-dev@ws.apache.org
Subject: [jira] Closed: (AXISCPP-193) Bad characters in complex type when set
 to null
In-Reply-To: <549947449.1097143853552.JavaMail.apache@nagoya>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Message:

   The following issue has been closed.

   Resolver: Mark Whitlock
       Date: Tue, 12 Oct 2004 8:37 AM

I have now fixed this problem by getting WSDL2WS to initialise all
fields of all complex types in their constructor.
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXISCPP-193

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXISCPP-193
    Summary: Bad characters in complex type when set to null
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

    Project: Axis-C++
 Components:=20
             Serialization/Deserialization
   Fix Fors:
             1.3 Final
   Versions:
             1.3 Final

   Assignee: Mark Whitlock
   Reporter: John Hawkins

    Created: Thu, 7 Oct 2004 3:10 AM
    Updated: Tue, 12 Oct 2004 8:37 AM

Description:

--- adrian.p.smith@bt.com wrote:

> OK.
>=20
> 1. I've edited the CH020XSoapPort.cpp file as suggested and, to stop the =
offending <pck> being
> returned, I have omitted it from the input. This seems to have highlighte=
d a further issue. When
> a complexType is sent in the request, if all the elements are left un-ini=
tialized, the SOAP
> payload has some wierd characters in the first element of the complex typ=
e. Output from YATT
> shows this:
>=20
> <?xml version=3D'1.0' encoding=3D'utf-8' ?><SOAP-ENV:Envelope
> xmlns:SOAP-ENV=3D"http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema"
> xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"><SOAP-ENV:Body><n=
s1:getCustomerProfile
> xmlns:ns1=3D"http://www.bt.com/css/mmbi/CH020X/"><mmbiInput xsi:type=3D"n=
s2:mmbiInput"
> xmlns:ns2=3D"http://www.bt.com/css/mmbi/2002/06/types"><correlId
> xsi:type=3D"xsd:string">=B0G1</correlId><trace xsi:nil=3D"true"/><locatio=
n
> xsi:nil=3D"true"/></mmbiInput><E2E xsi:type=3D"ns2:E2E"
> xmlns:ns2=3D"http://www.bt.com/css/mmbi/2002/06/types"><pck
> xsi:type=3D"xsd:string">=B0G1</pck><callerId xsi:nil=3D"true"/></E2E><tel=
Nr
>
xsi:type=3D"xsd:string">01208561489</telNr></ns1:getCustomerProfile></SOAP-=
ENV:Body></SOAP-ENV:Envelope>
>=20
> notice the =B0G1 in <correlId> and <pck>. Subsequent elements in the comp=
lexType are correctly
> sent as xsi:nil=3D"true". This causes a servlet error on the server side =
that results in a
> SOAP:Fault being returned, so we don't get to check out the de-serialisat=
ion. Is this another
> bug?
>=20


The WSDL from this issue is in Axis CPP 192


---------------------------------------------------------------------
JIRA INFORMATION:
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