Michael Glavassevich wrote:
Hello Murray,
The code you cited appears to be over four years old [1], so this doesn't
sound like new behaviour. Regardless of when this was introduced, it isn't
likely to change now. Both the HTMLSerializer and XHTMLSerializer were
deprecated in Xerces 2.6.2. We've been encouraging users to migrate their
code to use the standard JAXP Transformation API. If you're interested
about the future of Xerces serializers see this post [2] to xalan-dev from
February of this year.
[1]
http://cvs.apache.org/viewcvs.cgi/xml-xerces/java/src/org/apache/xml/serialize/HTMLSerializer.java?rev=1.10&view=markup
[2] http://marc.theaimsgroup.com/?l=xalan-dev&m=107593381313807&w=2
Michael,
Well, having investigated via trial implementation for the past few
days, I frankly can't say I'm very pleased with the changes. I went
from using my own code for serialization (a single class) to using
the original Xerces serializer (not too complicated) to using the
latest Xerces serializer (which now requires the whole factory
thing whilst not really providing any additional functionality,
just more complexity), then switching over to the Xalan code (I've
now lost some features, and found that it doesn't actually work,
as I'm getting some NoSuchMethodErrors, and I think all my jars are
completely up to date), and now, converting over to JAXP
Transformation API, I must download a 48MB shell script from Sun
just to obtain the jaxp-api.jar file (27K), plus I can no longer
freely distribute my entire application since I'm not allowed to
redistribute the 27K JAXP file (an API!). My target users are
non-technical, so I can barely expect them to get the latest version
of Java, much less download and install the JWSDP.
Having been a happy employee of Sun, I don't have any anti-Sun bias,
but we've gone from the simple idea of serializing a DOM tree to
an amazingly baroque solution that is no longer open source and
requires a *huge* download. We may have gained some interoperability
in the process, but I can't call that progress. I much prefer the
Xerces solution, even if I have to hack it to get it to do what I
want for CDATA sections. Too bad it was dumped in favour of Xalan.
And if Xalan comes up to fully supporting all of the Xerces
features, I still think moving to JAXP is a mistake. Even if I
have to rely on "proprietary" Apache code (I'm doing it already
just about everywhere), I prefer that over requiring the JWSDP.
Not to sound *too* negative, I'm interested in hearing more about
why this was considered a good idea. I read over the thread you
provided, but it didn't deal with the issues of complexity or
of the JWSDP requirement. Perhaps that's considered a given. If
it is, I hope that the Apache implementations stop deprecating
themselves unless the alternative is clearly better.
Murray
......................................................................
Murray Altheim http://kmi.open.ac.uk/people/murray/
Knowledge Media Institute
The Open University, Milton Keynes, Bucks, MK7 6AA, UK .
At a mobile home park in north Fort Pierce, Timothy Fellows
emerged from the storm to find a neighbor's trailer demolished
but only a fence down on his property. "My trailer survived!"
the barechested Fellows shouted as he walked through his yard.
"Because I believe in God. Even my mailbox survived. That tells
you something."
Ramiro Venegas, an itinerant worker from Mexico, said the storm
forced him to spend two nights sleeping in a men's toilet at a
Fort Pierce marina. He had been staying in his girlfriend's car
until she ditched him two days earlier.
http://www.sfgate.com/cgi-bin/article.cgi?f=/news/archive/2004/09/05/national1454EDT0524.DTL
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
