Arnaud Le Hors wrote:
>
> Character entities are not exposed through the DOM. The parser converts
> them right upfront. You should have the corresponding ampersand
> character in the element content though. Inside a Text node.
With xerces this happens only if the "feature"
http://apache.org/xml/f
Character entities are not exposed through the DOM. The parser converts
them right upfront. You should have the corresponding ampersand
character in the element content though. Inside a Text node.
--
Arnaud Le Hors - IBM Cupertino, XML Technology Group
Correction to last message
When I commented out
// parser.setFeature(
"http://xml.org/sax/features/external-general-entities";, false);
// parser.setFeature(
"http://xml.org/sax/features/external-parameter-entities";, false);
The setting
>
p.setFeature("http:/
(1) Using ORDER="all" in an archetype causes the following
exception to be thrown during parsing:
Unknown ContentSpecNode.NODE_XXX value at
org.apache.xerces.framework.XMLParser.reportError(XMLParser.java:1273) at
org.apache.xerces.validators.schema.XSchemaValida
(3) Using any sort of lexicalRepresentation in a datatype
causes the following exception to be thrown during parsing:
java.lang.NullPointerException at
java.util.Hashtable.put(Hashtable.java:381) at
org.apache.xerces.validators.schema.XSchemaValidator.traverseDat
Hi
I am having a problem with & dissappearing in the DOM when I use the
parser to create it.
I tried using the
p.setFeature("http://apache.org/xml/features/dom/create-entity-ref-nodes",false);
as suggested below, but it failed also when I looked at the node value
using the TreeWalker sample which
Bluestream - Boris Garbuzov wrote:
>
> Hello, guys. Can you please tell us how to join your Xerses news group
> or mailing list or refer us to right people? Particularly we have
> question how to handle ampersant "&" with your parser. If the text "Love
> & Sweetness" is a fragment of xml file, the
Yeah, I read the 12/17 version on Monday and sent appropriate comments to
www-xml-schema-comments. Between XLink, XPointer,
XFragment and XPath, I think external entities are covered but I still don't
see anything that replaces internal/text entities.
I haven't seen much direction on implementat
I think it is valuable to remain abstract in DOMString
since we may want to allow specific optimizations that
are not appropriate in a generic basic_string.
However, it might be possible to morph DOMString so
that it has identical semantics to a subset of
basic_string and could either be implement
Mark Lambert said:
>A couple of feature requests too:
> (1) support for the various date and time datatypes
> (2) support for pattern-matching lexical representations
> (3) support for nested element declarations
> (4) use of Java BigDecimal as the underlying type for XML Sc
Mark,
All of the schema stuff is at prototype stage,
since the spec keeps changing.
- Original Message -
From:
Mark Lambert
To: [EMAIL PROTECTED]
Sent: Tuesday, December 21, 1999 11:11
AM
Subject: bugs in XML4J 3.0 EA?
Obligatory disclaimer: I'm new to this li
This is also on the list for Xerces-J. See the STATUS file for
a complete list of tasks that need to be done.
- Original Message -
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, December 21, 1999 10:43 AM
Subject: Re: PROPOSAL: Document validation by overriding DTD.
>
George,
textEntity has been removed in the latest Working Draft.
If that is not to your liking, you can make your opinion known on
the xml-schema-comments mailing list.
http://lists.w3.org/Archives/Public/www-xml-schema-comments/
Ted
- Original Message -
From: "George T. Joseph" <[EMAIL
I just checked in a fix for this. Be aware that textEntity has gone away in
the
latest WD.
Ted
- Original Message -
From: "George T. Joseph" <[EMAIL PROTECTED]>
To: "xerces-dev" <[EMAIL PROTECTED]>
Sent: Wednesday, December 15, 1999 9:47 PM
Subject: NullPointerException in StringPool.addS
14 matches
Mail list logo
