Michael Glavassevich wrote:
Murray Altheim <[EMAIL PROTECTED]> wrote on 09/06/2004 11:11:38 AM:
[...]
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.
Murray,
I'm not sure what led you down this path. Both Xerces and Xalan (and I
imagine many other Apache projects) include the XML APIs with their
distributions. See xml-apis.jar. It orginates from xml-commons [1]. Anyone
who's downloaded the binary package for Xerces and/or Xalan already has
the SAX, DOM and JAXP interfaces.
Michael,
I'm going to obviously do more homework here. For some reason ant wasn't
finding the JAXP Transform API, despite my (as you indicate correctly)
already including the xml-apis.jar as part of any number of included
sub-projects. And of course, now that I peer into that jar I find the
API. I will admit I had no idea of the history of serialization within
the XML Apache project, and hadn't gathered that the Xerces code was
going to be deprecated until I installed 2.6.2. Having worked at Sun,
I was admittedly having a tough time believing that they would have
packaged the API only within the JWSDP. I was confused. (no duh)
I'm hoping to find out how to accomplish some of the things I could
do in the Xerces serializer that don't seem to be part of the Xalan
or JAXP serializers. I haven't yet found the canonical list of available
properties, and I'd RTFM if I could find it. Part of the problem, which
I hope you can understand, is that I wasn't dealing with serializers
or serialization at all a few days ago. I was trying to work on my
own project under a tight deadline. I needed for other reasons to
upgrade to 2.6.2 and suddenly, poof! the serialization world under my
feet changed. A scramble, and yet no simple solution. I've now gone
back to my older code and hacked Xerces to make things work, and at
some point when I have a bit more time I'll try again to figure out
how to get the JAXP-based serialization to work, i.e., why it wasn't
working this time around.
Thanks for your patience,
Murray
......................................................................
Murray Altheim http://kmi.open.ac.uk/people/murray/
Knowledge Media Institute
The Open University, Milton Keynes, Bucks, MK7 6AA, UK .
"If [bin Laden] has a watch, he should be looking at it because the
clock is ticking. He will be caught," said Joseph Cofer Black, the
U.S. State Department coordinator for counterterrorism.
http://www.sfgate.com/cgi-bin/article.cgi?file=/c/a/2004/09/06/MNG1Q8KH2E1.DTL
Where do they find people like this guy?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
