The Synapse script mediator has been migrated to BSF 3.0 now and is using the BSF 3.0-beta1-SNAPSHOT.
There's a RC1 available now of BSF 3.0, see http://marc.info/?l=bsf-dev&m=117479081324595&w=3. I hope to start the vote to release BSF 3.0-beta1 on Monday which hopefully get the release out before the end of the week. I'm away oh holiday after Friday so if there's any delays we may need to go back to BSF 2.4.0 in Synaspe so as not to block the Synapse release. If anyone can spare the time to review the BSF RC and the Synapse script mediator that would be really helpful. Thanks, ...ant On 3/16/07, ant elder <[EMAIL PROTECTED]> wrote:
Yep, will give it a start over this weekend. ...ant On 3/16/07, Asankha C. Perera <[EMAIL PROTECTED]> wrote: > > Hi Ant > > Do you think you would have the time to see how we could migrate to BSF > v3? As this will not affect the rest of Synapse, we could try this on a > low priority thread when time permits.. > > thanks > asankha > > Sanjiva Weerawarana wrote: > > +1 from me too! (And I'll hop over to the other side with my bsf hat > > on too ..) > > > > Sanjiva. > > > > Asankha C. Perera wrote: > >> Hi Ant > >>> The best way to resolve this is to use JSR-223 instead of Apache BSF > >>> v2 as JSR-223 script engines have an API to see if the engine is > >>> threadsafe. > >>> > >>> BSF version 3 is implementing JSR-223 and there's a beta1-SNAPSHOT > >>> available now but no proper release yet. I would have quite liked > >>> Synapse 1.0 to use BSF v3 but didn't want to get in the way of the > >>> release. We probably could get a BSF v3 beta1 release out quite > >>> quickly if Synapse said it would use it. Is there an interested in > >>> doing that? > >> Since we are not tied too much into BSF v2 anyway, I think it would > >> be good to move to V3. So if the BSF folks could get a beta1 release > >> out in the next couple of weeks, we could move our code to the V3 > >> beta1 snapshot in the meantime and check how we could use it. > >> > >> asankha > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
