Re: [Jsynthlib-devel] JDom dependancy

[Rib R. <ri...@gm...>]

On 3/6/06, Joe Emenaker <jo...@em...> wrote:
> Joe Emenaker wrote:
> > It's so much of an improvement that some are expecting that JDOM will
> > eventually be incorporated into J2SE
> > (http://www.jcp.org/en/jsr/results?id=3D93). So, part of why I decided
> > to include jdom.jar is because I expect that, someday, we'll be able
> > to remove it when JDOM (or some other object-oriented XML suite)
> > becomes part of the standard J2SE implementation.
> I stand corrected. It turns out that the author of JDOM has withdrawn
> their bid to get JDOM included in J2SE
> (http://www.jdom.org/pipermail/jdom-interest/2004-September/014191.html).
>
> This leaves me with four courses of action (in increasing preference):
>
> 1 - Leave jdom.jar in JSL. (This is the option I like least)
> 2 - Convert my code in JSL that does XML stuff to use JAXP
> 3 - Get the source code for JDOM and actually include just the parts
> that I need to use into the actual JSL source tree (license permitting).
> 4 - Write my own classes that behave like JDOM (ie, they would have an
> object-oriented front-end while using the yucky JAXP-DOM classes for the
> actual work).
>
> I'll have to take another look at JAXP and see how distasteful it is and
> then I'll decide.

I've already worked on something like #4 for the XML driver (although
it's not based on the JDOM api or anything like that).
If I have time I'll try to look at the stuff you've added and see how
hard it would be to convert to use the XML driver's SAX parser.

And on a side note, Groovy seems to be on schedule with their plans
for integration into J2SE.