Return-Path: Delivered-To: apmail-incubator-cxf-dev-archive@locus.apache.org Received: (qmail 46219 invoked from network); 31 Oct 2007 20:20:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 31 Oct 2007 20:20:24 -0000 Received: (qmail 79095 invoked by uid 500); 31 Oct 2007 20:20:11 -0000 Delivered-To: apmail-incubator-cxf-dev-archive@incubator.apache.org Received: (qmail 79050 invoked by uid 500); 31 Oct 2007 20:20:11 -0000 Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-dev@incubator.apache.org Delivered-To: mailing list cxf-dev@incubator.apache.org Received: (qmail 79041 invoked by uid 99); 31 Oct 2007 20:20:11 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Oct 2007 13:20:11 -0700 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of bim2007@basistech.com does not designate 199.88.205.99 as permitted sender) Received: from [199.88.205.99] (HELO mail.basistech.com) (199.88.205.99) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Oct 2007 20:20:15 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: Rhino DOM sadness, LGPL amplification Date: Wed, 31 Oct 2007 16:19:51 -0400 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Rhino DOM sadness, LGPL amplification Thread-Index: Acgb+2Qw/4t+f2kJTJ2OTd7Y2Vjx7Q== From: "Benson Margulies" To: X-Virus-Checked: Checked by ClamAV on apache.org I don't suppose that ASF makes any exception for the use of LGPL components used only for tests? I have the following sad story. I'm trying to get as much testing as possible of the JavaScript generator to happen in Rhino where we can automate it.=20 Sadly, Rhino skipped the DOM and went straight to E4X. I'm not interested in E4X as a target, since, for better or worse, I'm not interested in freezing out IE as a target for generated JavaScript. I have found an LGPL JavaScript DOM. I have also got the Google ajax/slt BSD-licensed DOM. It, however, is completely ignorant of namespaces, so it would take extra work to get it to go, and it is a poor model of what will happen in any of the real browsers. The last option may be the least bad option.