RE: [Rsslibj-developer] licenses

[Joseph O. <jo...@en...>]

On Fri, 7 Mar 2003, Danny Ayers wrote:

> > 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  ;-)

I've got a truck I'd like to replace with a vehicle I can stuff my family
in...

> 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?

Actually, J2SE 1.4 was the original target. I initially started coding,
thought, "Hey, JAXP is standard now, why don't we use that, since
virtually everyone will have it," started coding, discovered cruft after
cruft, decided the W3C designs APIs like OMG does (Motto: "We want to
expose APIs that no one will want to use. Here's 30 lines of code to do
something that one line should do."), and ran back to EXML, since it's got
a lot of nifty advantages that saved me from spending a week on support
code to get a project out.

---------------------------------------------------------
Joseph B. Ottinger                 jo...@en...
http://enigmastation.com                    IT Consultant