On 10/9/07, Tammo van Lessen <[EMAIL PROTECTED]> wrote: > > Hi Matthieu, > > 2007/10/9, Matthieu Riou <[EMAIL PROTECTED]>: > > On 10/9/07, Tammo van Lessen <[EMAIL PROTECTED]> wrote: > > > However this raises another question to the OS license experts of you: > > > Is it allowed to depend on Mozilla Rhino (MPL/GPL)? > > > > Unfortunately it's not. But others have had the same problem and came up > > with a solution: Apache BSF. We could rely on it as our interface to > the > > scripting engine and would allow support to other languages. Then Rhino > > would have to be part of the environment or if you use JDK 1.6 it's > already > > there. The cool side effect is support for Jython, JRuby and Beanshell > :) > Actually a great idea, however I had some troubles to enable E4X since > Rhino does not automatically translates org.w3c.dom.Node (java) into > XML (js) object and vice versa. I had to write a wrapper for that > translation which of course depends on Rhino classes.
The latest BSF code is starting to try to address this and provides some utility classes to help, see [1]. Its a bit rough and not yet finished but we use it successfully in Tuscany and Synapse going from Axiom OMElements to things like JavaScript/E4X and Ruby/ReXML. However, I read discussions on Rhino's bugzilla and on some other > apache lists [see refs], so according to them at least the most recent > Rhino version is released unter MPL 1.1 which should be with ASL 2.0. > What do you think? It would be great if we could directly use it. Thats correct, since Rhino 1.6R5 its been relicensed to MPL so is now ok to have the rhino jar as a binary dependency, see "Category B" dependencies at [2]. ...ant [1] https://svn.apache.org/repos/asf/jakarta/bsf/trunk/bsf3/bsf-utils/src/main/java/org/apache/bsf/xml/XMLHelper.java [2] http://www.apache.org/legal/3party.html
