AW: Parsing DTD 's with CDATA elements

Subjects

•	Home
•	VOTE Move XML Commons to Xerces
•	Commented: (XERCESJ 589) Bug with pattern restriction on long strings
•	: Xerces J 2 8 1 Release on Wednesday, September 13th
•	: Xerces J 2 9 0 Release on Wednesday, November 22nd
•	Commented: (XERCESJ 1066) Restriction+choice+substitutionGroup error
•	Commented: (XERCESJ 1178) Error getting prefix for an attribute with no n
•	Updated: (XERCESJ 1244) XMLSchemaValidator does not contribute element 's
•	Some consideration about the xerces DOM implementation
•	Updated: (XERCESJ 1066) Restriction+choice+substitutionGroup error
•	Commented: (XERCESJ 1227) Poor performance / OutOfMemoryError for sequenc
•	retain exception stack traces
•	Updated: (XERCESJ 1193) NPE or hang when parsing using the "continue afte
•	Future of NekoHTML
•	Commented: (XERCESJ 1203) NPE in XMLDTDProcessor
•	DOM Level 3 APIs for Xalan J and a new Xalan release (2 7 1)
•	: xml commons external 1 3 04 Release on Wednesday, November 22nd
•	Commented: (XERCESJ 1247) Incorrect location information on SAX when usin
•	XInclude exceptions how to mirror Xerces J functionality into Xerces C++?
•	First proposal on SoC project "Add support for the StAX (JSR 173) cursor API
•	: xml commons resolver 1 2 Release on Wednesday, November 22nd
•	Typo in RangeToken java Please check
•	Validator features
•	java lang ClassCastException when adopting Node
•	using the org apache xerces impl xs identity package
•	Updated: (XERCESJ 1257) buffer overflow in UTF8Reader for characters out
•	Problem with ref attributes and schema validation
•	Updated: (XERCESJ 122) XMLSchemaValidator does not contribute element 's d
•	Performance problem under load Xerces with Weblogic 9 x
•	remove ignored memory allocation
•	Commented: (XERCESJ 1177) SAXXMLStreamReader doesn 't always report namesp
•	Commented: (XERCESJ 977) Null pointer exception during DOM parsing
•	Commented: (XERCESJ 1197) Code cleanup for org apache xml serialize
•	Commented: (XERCESJ 1201) Initial contribution for StAX Event API
•	Updated: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special c
•	Commented: (XERCESJ 1199) SAXXMLStreamReader should attempt to register a
•	Commented: (XERCESJ 1061) Regex "$ " and "^ " characters treated as special
•	Updated: (XERCESJ 589) Bug with pattern restriction on long strings
•	StackOverflow
•	xerces Range unnecessarily not garbage collectable if not detached
•	Updated: (XERCESJ 1178) Error getting prefix for an attribute with no nam
•	Bug in xs:redefine
•	Commented: (XERCESJ 1204) Can not set XMLEntityResolver for LSParser
•	Updated: (XERCESJ 1253) Prototype for SoC2007 project "Add support for th
•	Updated: (XERCESJ 1259) Add SteamFilter Function to SoC2007 project "Add
•	Assigned: (XERCESJ 444) SAXException thrown by EntityResolver is reported
•	Google Summer of Code 2007
•	Xerces J and XInclude relative path issue
•	Assigned: (XERCESJ 206) Stack overflow when using a schema validation
•	Commented: (XERCESJ 1215) Restrictions involving two levels of substituti
•	Closed: (XERCESJ 1203) NPE in XMLDTDProcessor
•	non overriding equals methoda
•	Resolved: (XERCESJ 1079) invalid value returned for TOTALDIGITS facet in
•	Xerces AS3 port
•	Updated: (XERCESJ 325) Regular Expression; Pattern "\| " clause order de
•	Updated: (XERCESJ 1196) Javadoc generation fails on Java SE 5 0
•	Closed: (XERCESJ 1202) DTD validation on XIncluded documents when the sch
•	Created: (XERCESJ 1124) Nonspecific schema error message
•	a bug in xerces
•	Updated: (XERCESJ 1201) Initial contribution for StAX Event API
•	Closed: (XERCESJ 1254) Empty uris in targetNamespace attribute not report

Links

Home

Oracle database error code

AW: Parsing DTD 's with CDATA elements

AW: Parsing DTD 's with CDATA elements

2003-01-15 - By Hellmann Peter (ext) ICN CN 1F BD

i agree with Joe. i have successfully validated xml that contains a RFC822
mail within a CDATA section against a XSD file and it worked. the only thing
i did in the XSD file was to add the following:

<xs:element name="MAIL" type="xs:string">
</xs:element>

the CDATA doesn't need to be defined as a kind of "tag" or "sub-tag", it
simply encapsulates text that doesn't need to be escaped. the rfc822 mails i
embed have anyway carefully be checked for the 3 character end delimiter
"]]>" within the mail header and any mime-headers.

so i think if you change the last line of your DTD to <!ELEMENT initData
(#PCDATA)> all should work fine.

cheers,

Peter
-----Ursprüngliche Nachricht-----
Von: Greg Hess [mailto:ghess@(protected)]
Gesendet: Dienstag, 14. Januar 2003 22:26
An: Xerces User Mail list
Betreff: Parsing DTD's with CDATA elements

Hi All,

I have build a data structure that contains an element of type CDATA. When I
parse the xml data I get the error org.xml.sax.SAXParseException: A '('
character or an element type is required in the declaration of element type
"initData". Does anyone have any insight as to why my xml cannot be
validated by Xerces. It also displays fine when tested under IE when I
remove the # in #CDATA?

Many thanks,

Greg

<?xml version="1.0" encoding="UTF-8" ?>
<!DOCTYPE invocation (View Source for full doctype...)>
<http://localhost/instancemanager/testXML##> - <invocation>
<method>_import</method>
<id>1235768_69</id>
<typeName>sometype</typeName>
<http://localhost/instancemanager/testXML##> - <initData>
- <![CDATA[

<some>init</someuuu>
]]>
</initData>
</invocation>

The data is validated with the following dtd:

<?xml version="1.0" encoding="UTF-8"?>
<!ELEMENT invocation (method,id,typeName,initData)>
<!ELEMENT method (#PCDATA)>
<!ELEMENT id (#PCDATA)>
<!ELEMENT typeName (#PCDATA)>
<!ELEMENT initData (#CDATA)>

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">

<META content=Word.Document name=ProgId>
<META content="MSHTML 5.00.3502.5390" name=GENERATOR>
<META content="Microsoft Word 10" name=Originator><LINK
href="cid:filelist.xml@(protected)" rel=File-List><LINK
href="cid:editdata.mso@(protected)" rel=Edit-Time-Data>
<STYLE>@(protected) {
font-family: Courier;
}
@(protected) {
font-family: Verdana;
}
P.MsoNormal {
FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; mso
-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times
New Roman"
}
LI.MsoNormal {
FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; mso
-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times
New Roman"
}
DIV.MsoNormal {
FONT-FAMILY: "Times New Roman"; FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; mso
-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times
New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
PRE {
FONT-FAMILY: "Courier New"; FONT-SIZE: 10pt; MARGIN: 0in 0in 0pt; mso
-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman"
}
SPAN.EmailStyle17 {
COLOR: windowtext; FONT-FAMILY: Arial; mso-style-type: personal-compose; mso
-style-noshow: yes; mso-ansi-font-size: 10.0pt; mso-bidi-font-size: 10.0pt; mso
-ascii-font-family: Arial; mso-hansi-font-family: Arial; mso-bidi-font-family:
Arial
}
SPAN.tx1 {
FONT-WEIGHT: bold; mso-style-name: tx1
}
SPAN.m1 {
COLOR: blue; mso-style-name: m1
}
SPAN.pi1 {
COLOR: blue; mso-style-name: pi1
}
SPAN.b1 {
COLOR: red; FONT-FAMILY: "Courier New"; FONT-WEIGHT: bold; TEXT-DECORATION:
none; text-underline: none; mso-ascii-font-family: "Courier New"; mso-hansi
-font-family: "Courier New"; mso-bidi-font-family: "Courier New"; mso-style-name
: b1; mso-text-animation: none; text-line-through: none
}
SPAN.d1 {
COLOR: blue; mso-style-name: d1
}
SPAN.t1 {
COLOR: #990000; mso-style-name: t1
}
SPAN.di1 {
FONT-FAMILY: Courier; mso-ansi-font-size: 12.0pt; mso-bidi-font-size: 12.0pt;
mso-ascii-font-family: Courier; mso-hansi-font-family: Courier; mso-style-name:
di1
}
SPAN.SpellE {
mso-style-name: ""; mso-spl-e: yes
}
SPAN.GramE {
mso-style-name: ""; mso-gram-e: yes
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=EN-US link=blue style="tab-interval: .5in" vLink=purple>
<DIV>i
agree with Joe. i have successfully validated xml that contains a
RFC822 mail within a CDATA section against a XSD file and it worked. the only
thing i did in the XSD file was to add the following:</DIV>
<DIV> </DIV>
<DIV><xs:element name="MAIL"
type="xs:string">   </xs:element></DIV>
<DIV> </DIV>
<DIV>the
CDATA doesn't need to be defined as a kind of "tag" or "sub-tag", it simply
encapsulates text that doesn't need to be escaped. the rfc822 mails i embed
have anyway carefully be checked for the 3 character end delimiter "]]>" within
the mail header and any mime-headers.</DIV>
<DIV> </DIV>
<DIV>so
i
think if you change the last line of your DTD to <!ELEMENT
 initData (#PCDATA)> all should work
fine.
<o:p></o:p></DIV>
<DIV> </DIV>
<DIV>cheers,</DIV>
<DIV> </DIV>
<DIV>Peter   </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px;
PADDING-LEFT: 5px">
<DIV align=left class=OutlookMessageHeader dir=ltr>-----Ursprüngliche Nachricht----- Von: Greg Hess
[mailto:ghess@(protected)] Gesendet: Dienstag, 14. Januar 2003
22:26 An: Xerces User Mail list Betreff: Parsing DTD's
with CDATA elements </DIV>
<DIV class=Section1>
Hi
All,<o:p></o:p>
<o:p> </o:p>
I have build a data structure that contains an element of type
CDATA. When I parse the xml data I get the error org.xml.sax.SAXParseException: A '(' character or an element
type is required in the declaration of element type "initData". Does anyone have any insight as to why my xml
cannot be validated by Xerces. It also displays fine
when tested under IE when I remove the # in
#CDATA?<o:p></o:p>
<o:p> </o:p>

Many
thanks,<o:p></o:p>
<o:p> </o:p>

Greg<o:p></o:p>
<o:p> </o:p>
<o:p> </o:p>
<?xml
 version="1.0" encoding="UTF-8"

?>
<o:p></o:p>
  <!DOCTYPE
invocation (View Source for full doctype...)>
<o:p></o:p>
<A
href="http://localhost/instancemanager/testXML##" onclick="return false"
onfocus=h()>-</A>
    <invocation><o:p></o:p>
              
 
<method>_import</method> <o:p></o:p>
              
 
<id>1235768_69</id> <o:p></o:p>
              
 
<typeName>sometype</typeName> <o:p></o:p>
<A
href="http://localhost/instancemanager/testXML##" onclick="return false"
onfocus=h()>-</A>
        
 
<initData><o:p></o:p>
-          
         
<![CDATA[ <o:p></o:p><PRE style="TEXT-INDENT
: -12pt">   
              <some>init</someuuu><o:p></o:p></PRE>
         
    
]]>
<SCRIPT>
f(clean);
</SCRIPT>
<o:p></o:p>
          
 
</initData><o:p></o:p>
  </invocation><o:p></o:p>
<o:p> </o:p>

   The data is validated with the
following dtd:<o:p></o:p>
<o:p> </o:p>

   <?xml
version="1.0" encoding="UTF-8"?><o:p></o:p>
<!ELEMENT invocation (method,id,typeName,initData)><o:p></o:p>

<!ELEMENT method
(#PCDATA)><o:p></o:p>
<!ELEMENT id
(#PCDATA)><o:p></o:p>
<!ELEMENT typeName (#PCDATA)><o:p></o:p>
<!ELEMENT initData (#CDATA)>
<o:p></o:p>
<o:p> </o:p>
<o:p> </o:p>
<o:p> </o:p></DIV></BLOCKQUOTE
></BODY></HTML>