Return-Path: 
 <axis-dev-return-27760-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 29064 invoked from network); 14 Apr 2004 17:26:54 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 14 Apr 2004 17:26:54 -0000
Received: (qmail 28867 invoked by uid 500); 14 Apr 2004 17:26:42 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 28792 invoked by uid 500); 14 Apr 2004 17:26:39 -0000
Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
list-help: <mailto:axis-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@ws.apache.org>
list-post: <mailto:axis-dev@ws.apache.org>
Delivered-To: mailing list axis-dev@ws.apache.org
Received: (qmail 28590 invoked from network); 14 Apr 2004 17:26:38 -0000
Received: from unknown (HELO burn.fatwire.com) (209.212.94.2)
  by daedalus.apache.org with SMTP; 14 Apr 2004 17:26:38 -0000
Received: from mail.fatwire.com ([209.212.94.131]) by burn.fatwire.com;
 Wed, 14 Apr 2004  -0400 (Eastern Daylight Time)
Received: from burn.fatwire.com ([209.212.94.129]) by mail.fatwire.com
           (Netscape Messaging Server 3.6)  with SMTP id 99;
           Wed, 14 Apr 2004 13:30:44 -0400
Received: from cpe00c049e0ca16-cm014250012931.cpe.net.cable.rogers.com
 ([65.50.66.134]) by burn.fatwire.com;
 Wed, 14 Apr 2004  -0400 (Eastern Daylight Time)
In-Reply-To: <05a701c421f2$66afdc60$0200a8c0@Gary005>
References: <05a701c421f2$66afdc60$0200a8c0@Gary005>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <D59B50F6-8E38-11D8-9A3C-000A95DA4BDA@fatwire.com>
Content-Transfer-Encoding: quoted-printable
Cc: Karl Wright <kwright@FatWire.com> 	,
  Tony Field <tony.field@fatwire.com> 	,
  Pradeep Aradhya <paradhya@FatWire.com>
From: Tony Field <tony.field@fatwire.com>
Subject: Re: invalid character question
Date: Wed, 14 Apr 2004 13:26:16 -0400
To: axis-dev@ws.apache.org
X-Mailer: Apple Mail (2.613)
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

Thank you Gary, that explains my question exactly.  I did not=20
understand that you couldn't even have a reference to an invalid=20
character in a well-formed xml document.

Tony

On 14-Apr-04, at 3:30 AM, Gary L Peskin wrote:

> As indicated in your cited reference to the XML 1.0 Recommendation,=20
> the character $#28 is -not- a valid XML 1.0 character (ie Char) and=20
> cannot appear in a well-formed XML document.=A0 This is true =
regardless=20
> of whether the character appears directly or through a character=20
> reference.=A0 Whether it appears inside or outside of a CDATA section =
is=20
> of no consequence whatsoever.=A0 The CDATA section is provided to=20
> include < and & without the need to escape them (which is required in=20=

> a non-CDATA section).=A0
>  =A0
> HTH,
> Gary
> -----Original Message-----
> From: Tony Field [mailto:tony.field@fatwire.com]
>  Sent: Tuesday, April 13, 2004 1:33 PM
> To: axis-dev@ws.apache.org
> Subject: invalid character question
>
> Hello,
> This is my first post to this list, so I apologize if this issue has=20=

> been addressed.
> I'm using Axis as a client to a web service. The client stubs were=20
> generated using wsdl2java. Everything seems to work well for me,=20
> except when my XML document body contains the 1C character. To get=20
> around this, our web service encloses our document data in a cdata=20
> block. When we encounter a character that is not valid (per=20
> http://www.w3.org/TR/2004/REC-xml-20040204/#charsets), we close the=20
> cdata block and escape the character using &#refNo; for each invalid=20=

> character, then re-open the cdata block and continue with the=20
> document.
> So, for example a document may look like this:
>
> <item><![CDATA[The words ]]>&#28;<![CDATA[what is in your=20
> wallet]]></item>
> The problem I'm having is that the axis client is throwing an=20
> exception parsing the response with this data in it. The exception=20
> thrown is listed below. Why is axis failing to parse this response? I=20=

> see the failure using both xerces and crimson. A colleague has tested=20=

> this using XMLSpy and it does not fail to parse the response - the=20
> response looks exactly like what I show above.
> Any help would be greatly appreciated.
> Sincerely,
> Tony