Re: Why are we still using JAXP and ProjectX??? (proprietary==evil)

2001-01-09 Thread Kevin A. Burton
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 James Duncan Davidson [EMAIL PROTECTED] writes: On 1/3/01 10:24 PM, "Kevin A. Burton" [EMAIL PROTECTED] wrote: Why are we using JAXP and ProjectX which are both Closed Source and proprietary to SUN Microsystems. This is a Bad Thing. We

Re: Why are we still using JAXP and ProjectX??? (proprietary==evil)

2001-01-09 Thread Kevin A. Burton
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jon Stevens [EMAIL PROTECTED] writes: on 1/3/2001 10:24 PM, "Kevin A. Burton" [EMAIL PROTECTED] wrote: Ug. Checked over the archives and didn't see this Why are we using JAXP and ProjectX which are both Closed Source and proprietary

Re: Why are we still using JAXP and ProjectX???(proprietary==evil)

2001-01-08 Thread Christopher K. St. John
James Duncan Davidson wrote: On 1/3/01 10:24 PM, "Kevin A. Burton" [EMAIL PROTECTED] wrote: Why are we using JAXP and ProjectX which are both Closed Source and proprietary Then why are you using Java which is composed of code most of which isn't under a free license There are

Re: Why are we still using JAXP and ProjectX???(proprietary==evil)

2001-01-08 Thread Sam Ruby
James Duncan Davidson wrote: What I'm saying is that you can redist the jaxp.jar file containing the classes of the implementation. That's what we need to be doing in the Apache tree anyway since we don't have a source redistribution license. IMHO, we should have a cleanroom

Re: Why are we still using JAXP and ProjectX???(proprietary==evil)

2001-01-08 Thread James Duncan Davidson
On 1/8/01 9:31 AM, "Sam Ruby" [EMAIL PROTECTED] wrote: IMHO, we should have a cleanroom re-implementation of this important API. If the current codebase in Apache doesn't meet this criteria, this problem should be addressed ASAP. The implementation in the current Xerces tree is a fine clean

Re: Why are we still using JAXP and ProjectX???(proprietary==evil)

2001-01-07 Thread James Duncan Davidson
On 1/3/01 10:24 PM, "Kevin A. Burton" [EMAIL PROTECTED] wrote: Why are we using JAXP and ProjectX which are both Closed Source and proprietary to SUN Microsystems. This is a Bad Thing. We already have an awesome XML parser and I would say just *drop* the abstraction... not worth the loss

Re: Why are we still using JAXP and ProjectX??? (proprietary==evil)

2001-01-04 Thread Sam Ruby
Kevin Burton wrote: Ug. Checked over the archives and didn't see this Why are we using JAXP and ProjectX which are both Closed Source and proprietary to SUN Microsystems. This is a Bad Thing. We already have an awesome XML parser and I would say just *drop* the abstraction... not worth

Why are we still using JAXP and ProjectX??? (proprietary==evil)

2001-01-03 Thread Kevin A. Burton
Ug. Checked over the archives and didn't see this Why are we using JAXP and ProjectX which are both Closed Source and proprietary to SUN Microsystems. This is a Bad Thing. We already have an awesome XML parser and I would say just *drop* the abstraction... not worth the loss of Freedom :(.

Re: Why are we still using JAXP and ProjectX??? (proprietary==evil)

2001-01-03 Thread Rajiv Mordani
-- :wq On Wed, 3 Jan 2001, Jon Stevens wrote: on 1/3/2001 10:24 PM, "Kevin A. Burton" [EMAIL PROTECTED] wrote: Ug. Checked over the archives and didn't see this Why are we using JAXP and ProjectX which are both Closed Source and proprietary to SUN Microsystems. This is a