RE: [Rsslibj-developer] licenses

[Danny A. <dan...@vi...>]

[snip - all fair enough!]

> Actually, this has something to do with why we chose EXML, too: because
> the existing user base with Xerces was a known quantity. If we used Xerces
> (or, if you like, JAXP - they're not the same, as is par for Sun's
> course), we'd be binding in a version dependency. Thus, people who were
> using Xerces would then be trapped into using *our* version of Xerces...
> and vice versa. (True story: I know of a project that has to have TWO
> versions of xerces in the same project. Lovely concept.) EXML's smaller
> userbase means that deployers can drop it in without expecting the rest of
> their xerces-dependent code to have any changes whatsoever.

Heh, I must admit this angle hadn't occurred to me - I love it.
I've been caught out by version dependency and associated problems often
enough, worst of all was when I was using Crimson (in Batik) alongside
Xerces (in Jena). Usually didn't have a clue which version of a class was
being used. I actually think I've got 3 different versions of Xerces around
as we speak (one in my dev tree, I think there's one tucked into a local
Tomcat install, and another in Jena). So your arguments above have a
sympathetic ear here - in fact if you've any used cars you want to sell, now
would be a very good time  ;-)

There is another consideration, and I'd very much like to hear your
thoughts - J2SE 1.4 with its XML support. At which point do you think it
would make sense in a project like this to move the focus to this version?

Cheers,
Danny.