You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2002/09/07 00:35:57 UTC
DO NOT REPLY [Bug 10989] -
DTDGrammar - getContentSpec
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10989>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10989
DTDGrammar - getContentSpec
neilg@ca.ibm.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |WONTFIX
------- Additional Comments From neilg@ca.ibm.com 2002-09-06 22:35 -------
Hi. This method probably shouldn't be public--contentSpecIndexes are very much
part of the internal workings of Xerces DTDGrammar structure, and only the very
bravest of hackers should probably be looking at them. And if anyone does,
they'll probably be doing it for reasons that require them to make more tweaks
than just changing a method from, say package-protected to public.
Anyway, contentSpecIndexes get used to build contents models during DTD
parsing/reading of element declarations. Then, once the content models are
created, they get used as Xerces traverses the document--XMLContentSpec objects
carry appropriate indexes with them.
All that said, I don't really think its worthwhile actually changing the
visibility of this method; it's possible there's an application happily using
it and there's no sense breaking it. But if you're prepared to delve this
deep, good luck--you're in unsupported waters!
If you have more questions, please post to the xerces-j-dev list; this is only
meant for bug-reporting.
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org