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
 
Search:  
Power your search with and, or, +, -, or "some phrase" operators.
: Xerces-J 2.3.0 now available

: Xerces-J 2.3.0 now available

2003-01-30       - By Soosai, Lourdhu Vasanth
Reply:     1     2     3     4     5     6  

hi,
       iam trying to change the value of a text node using SAX parser.
     
       iam able to do it for attributes..(eg:attributesImpl.setValue(3,
"donotcontact");)
       how can i change the characters value while parsing using SAX
       like
               <name > nameOne</name>
             
               how would i change it to
             
                       <name > nameTwo</name>
               without really constructing a string buffer.
thx
vasanth



-----Original Message-----
From: neilg@(protected) [  <mailto:neilg@(protected)> mailto:neilg@(protected)]
Sent: Monday, January 27, 2003 6:43 PM
To: xerces-j-dev@(protected); xerces-j-user@(protected);
general@(protected); announcements@(protected)
Subject: [ANNOUNCEMENT]: Xerces-J 2.3.0 now available


Hi all,

The Xerces-J team is very happy to announce that version 2.3.0 of Xerces-J
is now available.  With this release, the Xerces-J developers are declaring
the Xerces Native Interface (XNI) core and parsers packages to be gold.
This release also brings Xerces-J into compliance with the most recent work
of the W3C DOM working group on DOM level 3 Core and Load/Save, and
introduces many fixes to bring Xerces-J's behaviour into line with XML
Schema errata. Support for the parsing of documents written according to
the XML 1.1 candidate recommendation has also been completed, except that
no option for verifying that documents are normalized has yet been
implemented. Finally, Xerces-J now provides means by which applications can
force the parser to reject certain kinds of documents whose processing
could result in a denial-of-service attack.

Specifically, the significant changes introduced in this release are:

- Modified XMLLocator interface to remove setter methods for move towards
finalizing XNI; this change also implied removing XMLLocator's dependence
upon XMLResourceIdentifier. [Andy Clark]
- Implemented several DOM Level 3 features, including DOMConfiguration,
exposing type information via DOM, and allowing to set an ID attribute in
the DOM. [Elena Litani]
- Modified support for DOM L3 compareDocumentPosition (formerly
compareTreePosition). [Lisa Martin]
- Modified several XNI interfaces, i.e. NamespaceContext,
XMLResourceIdentifier, Augmentation, XMLAttributes, and updated
implementation accordingly.
[Elena Litani, Sandy Gao]
- Modified PSVI interfaces (org.apache.xerces.impl.xs.psvi) and updated
implementation accordingly. [Elena Litani]
- Modified XMLDTDHandler, XMLDTDSource, XMLDTDContentModelHandler and
XMLDTDContentModelSource to make these pipelines doubly-linked, as was done
in the last release for the main document pipeline. [Neil Graham]
- Completed experimental support for XML 1.1 and XML Namespaces 1.1 CR's,
except for XML 1.1 section 2.13. [Neil Graham]
- Provided a mechanism by which applications can instruct the parser to
abort the parsing of documents containing constructs that could swamp
system resources. [Neil Graham, Neeraj Bajaj]
- Added a feature "disallow-doctype-decl" so that a fatal error is reported
if this feature is on and the incoming document has a DOCTYPE. [Sandy Gao]
- Added a feature "standard-uri-conformant" so that the parser enforces the
URI rules when this feature is on. [Sandy Gao]
- Performance update: ported the partial DTM implementation of DOM and use
it for parsing Schema documents. [Sandy Gao]
- Provided full support for canonical representation of XML Schema
datatypes. [Sandy Gao]
- Implemented XML Schema errata as they were published. [Sandy Gao]
- Fix comment parsing bug that prevented Tomcat 4.1.12 from making use of
Xerces versions later than 2.1.0. [Tim Bruce, Neil Graham]

The release can be downloaded from
<http://xml.apache.org/dist/xerces-j/> http://xml.apache.org/dist/xerces-j/

Enjoy!
Neil
Neil Graham
XML Parser Development
IBM Toronto Lab
Phone:  905-413-3519, T/L 969-3519
E-mail:  neilg@(protected)



---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)



This e-mail may contain confidential or privileged information.  If you
think you have received this e-mail in error, please advise the sender by
reply e-mail and then delete this e-mail immediately.  Thank you.  Aetna

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE></TITLE>

<META content="MSHTML 5.50.4611.1300" name=GENERATOR></HEAD>
<BODY>
<P><FONT size=2>hi,<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; iam trying to
change the value of a text node using SAX
parser.<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;
iam able to do it for attributes..(eg:<FONT
color=#008000><STRONG>attributesImpl.setValue(3,
"donotcontact");)</STRONG></FONT><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
how can i change the characters value while parsing using
SAX<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
like<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;name &gt;
nameOne&lt;/name&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; how would i change it
to<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;name &gt;
nameTwo&lt;/name&gt;<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; without really constructing a string
buffer.<BR>thx<BR>vasanth<BR><BR><BR><BR>-----Original Message-----<BR>From:
neilg@(protected) [</FONT><A href="mailto:neilg@(protected)"><FONT
size=2>mailto:neilg@(protected)</FONT></A><FONT size=2>]<BR>Sent: Monday,
January
27, 2003 6:43 PM<BR>To: xerces-j-dev@(protected);
xerces-j-user@(protected);<BR>general@(protected);
announcements@(protected)<BR>Subject: [ANNOUNCEMENT]: Xerces-J 2.3.0 now
available<BR><BR><BR>Hi all,<BR><BR>The Xerces-J team is very happy to announce
that version 2.3.0 of Xerces-J<BR>is now available.&nbsp; With this release,
the
Xerces-J developers are declaring<BR>the Xerces Native Interface (XNI) core and
parsers packages to be gold.<BR>This release also brings Xerces-J into
compliance with the most recent work<BR>of the W3C DOM working group on DOM
level 3 Core and Load/Save, and<BR>introduces many fixes to bring Xerces-J's
behaviour into line with XML<BR>Schema errata. Support for the parsing of
documents written according to<BR>the XML 1.1 candidate recommendation has also
been completed, except that<BR>no option for verifying that documents are
normalized has yet been<BR>implemented. Finally, Xerces-J now provides means by
which applications can<BR>force the parser to reject certain kinds of documents
whose processing<BR>could result in a denial-of-service
attack.<BR><BR>Specifically, the significant changes introduced in this release
are:<BR><BR>- Modified XMLLocator interface to remove setter methods for move
towards<BR>finalizing XNI; this change also implied removing XMLLocator's
dependence<BR>upon XMLResourceIdentifier. [Andy Clark]<BR>- Implemented several
DOM Level 3 features, including DOMConfiguration,<BR>exposing type information
via DOM, and allowing to set an ID attribute in<BR>the DOM. [Elena Litani]<BR>-
Modified support for DOM L3 compareDocumentPosition
(formerly<BR>compareTreePosition). [Lisa Martin]<BR>- Modified several XNI
interfaces, i.e. NamespaceContext,<BR>XMLResourceIdentifier, Augmentation,
XMLAttributes, and updated<BR>implementation accordingly.<BR>[Elena Litani,
Sandy Gao]<BR>- Modified PSVI interfaces (org.apache.xerces.impl.xs.psvi) and
updated<BR>implementation accordingly. [Elena Litani]<BR>- Modified
XMLDTDHandler, XMLDTDSource, XMLDTDContentModelHandler
and<BR>XMLDTDContentModelSource to make these pipelines doubly-linked, as was
done<BR>in the last release for the main document pipeline. [Neil Graham]<BR>-
Completed experimental support for XML 1.1 and XML Namespaces 1.1
CR's,<BR>except for XML 1.1 section 2.13. [Neil Graham]<BR>- Provided a
mechanism by which applications can instruct the parser to<BR>abort the parsing
of documents containing constructs that could swamp<BR>system resources. [Neil
Graham, Neeraj Bajaj]<BR>- Added a feature "disallow-doctype-decl" so that a
fatal error is reported<BR>if this feature is on and the incoming document has
a
DOCTYPE. [Sandy Gao]<BR>- Added a feature "standard-uri-conformant" so that the
parser enforces the<BR>URI rules when this feature is on. [Sandy Gao]<BR>-
Performance update: ported the partial DTM implementation of DOM and use<BR>it
for parsing Schema documents. [Sandy Gao]<BR>- Provided full support for
canonical representation of XML Schema<BR>datatypes. [Sandy Gao]<BR>-
Implemented XML Schema errata as they were published. [Sandy Gao]<BR>- Fix
comment parsing bug that prevented Tomcat 4.1.12 from making use of<BR>Xerces
versions later than 2.1.0. [Tim Bruce, Neil Graham]<BR><BR>The release can be
downloaded from<BR></FONT><A target=_blank
href="http://xml.apache.org/dist/xerces-j/"><FONT
size=2>http://xml.apache.org/dist/xerces-j/</FONT></A><BR><BR><FONT
size=2>Enjoy!<BR>Neil<BR>Neil Graham<BR>XML Parser Development<BR>IBM Toronto
Lab<BR>Phone:&nbsp; 905-413-3519, T/L 969-3519<BR>E-mail:&nbsp;
neilg@(protected)<BR><BR><BR><BR>-----------------------------------------------
----------------------<BR>To
unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)<BR>For additional
commands, e-mail: xerces-j-user-help@(protected)<BR></FONT></P></BODY></HTML>
<BR>

<P><FONT SIZE=2 FACE="Arial">This e-mail may contain confidential or privileged
information.  If you think you have received this e-mail in error, please
advise the sender by reply e-mail and then delete this e-mail immediately.
Thank you.  Aetna</FONT></P>