Hi,
I have just downloaded and done some testing with xerces 2. I have some
further comments:
1. Features and Properties of DOMParsers:
from the JAXP documentation:
**********************************
setAttribute
public abstract void setAttribute(java.lang.String name,
java.lang.Object value)
throws java.lang.IllegalArgumentException
Allows the user to set specific attributes on the underlying implementation.
*************************
Because DOM defines no own features and properties these attributes are always
implementation dependent.
May be, that in the future there are standard attributes. So an application must
always(!) handle this problem.
Therefore why not mapping setAttribute(...) to the features and properties. This would
allow to use JAXP as highest
level API for SAX and DOM. For Xerces 1 you have done this mapping.
2. General comment to JAXP
I have written a comment to the Sun process directly and because there is no way to
get a response I don´t no the actual
state and the plans for the future. But if we remember how TRAX comes to JAXP may be
that you have more influence.
So what do you think about the following:
In my opinion it would be a good idea to put a advanced grammar support (DTD, XML
Schema, Relax, grammar caching, etc.) to the JAXP Level.
The transform package shows how such things may be done.
May be it makes sense to have two levels on the JAXP level also for the parser package.
If nothings happens JAXP will be obsolete in the near future, because JAXP 1.2 does
not provide enough functionality for
server side applications using Schemata for XML.
Regards
Thomas
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
