Andy Clark wrote:
>
> I'm working on revamping the docs for Xerces2 in preparation
> for a beta release. And at this time I'd like to float an
> idea past people to see what they think...
>
> I'd like to remove the WML and HTML DOM implementations
> from the package. I think that they're only being used by
> a few people and *noone* is maintaining them. I'm tempted
> to do the same with the serializers but most people need
> that functionality and we don't have a reasonable
> alternative at this time. (What about the serializers in
> Xalan? Are they equivalent? Whatever we decide, I'd like
> to have the serializers TrAX compatible.)
As for serializers, apps that use the API will be dependent on the
Apache Xerces implementation and would not be able to use a different
parser. For example, Apache crimson or other non-apache parsers do not
support this API. DOM level 3 will support this but it is not out yet.
JAXP 1.1 supports a parser independent way of doing this, but it
requires TrAX (transform) support which implies using an XSLT processor
such as Xalan. I think the cleanest solution currently would be to use
JAXP so apps would be portable. The problem is creating a distribution
that supports both the parsing and transform portions of JAXP. Does
Xalan-J already provide this? I know that they bundle Xerces so maybe
we can point users that want serialization support to the Xalan/Xerces
bundle as a full JAXP implementation.
>
> So what do people think? Would it be unreasonable to pull
> the WML and HTML DOM implementations out of the package
> at this time? We have never addressed the problem we have
> with contributed code. I'd vote for a separate package and
> download of user-donated code.
+1, sounds good to me. I'd support moving portions of code that are not
maintained and which few people use to a separate package.
-Edwin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
