Ant, Thanks for the great effort on this.
This should be OK. Even though we have planned for late this week as the code freeze, if it is going to be just a change in version + some additional work to get the axiom-E4X. Asankha, WDYT? Thanks, Ruwan On Oct 30, 2007 2:41 PM, ant elder <[EMAIL PROTECTED]> wrote: > JRuby 1.0.1 does work with the latest BSF. > > Looks like we may be able to start voting on the BSF beta2 release tomorrow > so hopefully will have a release out early next week if thats soon enough > for the Synapse 1.1 release. > > The latest BSF code should also support the wso2 axiom-e4x impl and should > use that automatically when the axiom-e4x jar is in the classpath. Had to > do a couple of hacks to get that to work which I'll bring up here in case > there's someone listening who knows about axiom-e4x. > > One is that there needs to be a way to register the AxiomE4XContextFactory > before anything uses JavaScript, so before calling BSF you need to call > org.apache.bsf.xml.XMLHelper.init(), eg the testcase [1], we'd need to > update the Synapse script mediator to do that for this to work in Synapse. > This doesn't seem great but probably not much we can do. > > Another is that when using the axiom-e4x impl you get an NPE in Rhino if you > try to get E4X XML from an OMElement outside of a running script as the > Scope isn't set up correctly. This works for the non-axiom-e4x impl so it > may be a bug in axiom-e4x. Had to use a helper class in the > org.mozilla.javascript package to get access to fix this which is a bit > nasty, see the ContextHelper.setTopCallScope call in [2]. > > ...ant > > [1] > https://svn.apache.org/repos/asf/jakarta/bsf/trunk/bsf3/testing/e4x-1.6R7-Axiom/src/test/java/org/apache/bsf/testing/e4x/HelloTestCase.java > [2] > https://svn.apache.org/repos/asf/jakarta/bsf/trunk/bsf3/bsf-utils/src/main/java/org/apache/bsf/xml/JavaScriptE4XAxiomHelper.java > > > > On 10/27/07, Ruwan Linton <[EMAIL PROTECTED]> wrote: > > Paul, > > > > JRuby 1.0.1 has an API conflict with the BSF engine. Once dims also talked > about this on the list [1], there you can find the exact issue. I think this > is fixed in the BSF-3.0 (as per ant) > > > > [1] - http://marc.info/?l=synapse-dev&m=118971603705850&w=2 > > > > Thanks, > > Ruwan > > > > > > > > On 10/27/07, Paul Fremantle <[EMAIL PROTECTED]> wrote: > > > Ruwan > > > > > > What's the problem with JRuby? > > > > > > Can you please post a detailed description - if Ant is going to do an > update it would be fantastic if he could include any bugfixes for JRuby too. > > > > > > Paul > > > > > > > > > On 10/27/07, Ruwan Linton <[EMAIL PROTECTED] > wrote: > > > > > > > Paul, > > > > > > > > AFAIK, we can not go with the version of scripting languages that we > want, rather we have to live with the version of the particular scripting > language supported by the particular BSF version that we are using (this is > because scripting language API is changing, nothing to do with BSF). We are > facing the same issue with JRuby as well. It is better if we can get a BSF > release with support for all the new versions of Scripting languages > including Jython, Jruby, Groovy etc.But I don't think our time frame for the > 1.1 release is going to scale for this???? > > > > > > > > Thanks, > > > > Ruwan > > > > > > > > > > > > On 10/26/07, Paul Fremantle < [EMAIL PROTECTED]> wrote: > > > > > > > > > Deepal > > > > > > > > > > Its deploying Groovy as a mediator. Please see > http://ws.apache.org/synapse/Synapse_Samples.html#Sample500 > > > > > for more information about the script support in Synapse. > > > > > > > > > > Paul > > > > > > > > > > > > > > > > > > > > On 10/26/07, Deepal jayasinghe < [EMAIL PROTECTED]> wrote: > > > > > > Paul Fremantle wrote: > > > > > > > Folks > > > > > > > > > > > > > > I was recently presenting on Groovy and Synapse at the Grails > Exchange > > > > > > > conference. There is an RC1 out for Groovy 1.1 and a lot of > updates, > > > > > > > and I think it would be great to update to Groovy 1.1 in our 1.1 > > > > > > > release. Unfortunately, they changed the interface so its not > > > > > > > compatible - I already tried just dropping the 1.1-RC1 release > into > > > > > > > Synapse and it doesn't work. > > > > > > > > > > > > > > Any chance we can do this in time for Synapse 1.1? > > > > > > Paul , > > > > > > What do you mean by supporting Groovy , is that deploying groovy > class > > > > > > as a service ? if that is the case I would like to implement that > first > > > > > > in Axis2 and allow Synapse to use that. > > > > > > > > > > > > Thanks > > > > > > Deepal > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Paul Fremantle > > > > > Co-Founder and VP of Technical Sales, WSO2 > > > > > OASIS WS-RX TC Co-chair > > > > > > > > > > blog: http://pzf.fremantle.org > > > > > [EMAIL PROTECTED] > > > > > > > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > > > > > > > > > > > > > -- > > > > Ruwan Linton > > > > http://www.wso2.org - "Oxygenating the Web Services Platform" > > > > > > > > > > > > > > > -- > > > Paul Fremantle > > > Co-Founder and VP of Technical Sales, WSO2 > > > OASIS WS-RX TC Co-chair > > > > > > blog: http://pzf.fremantle.org > > > [EMAIL PROTECTED] > > > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > > > > > -- > > Ruwan Linton > > http://www.wso2.org - "Oxygenating the Web Services Platform" > > -- Ruwan Linton http://www.wso2.org - "Oxygenating the Web Services Platform"
