On Wed, Jun 11, 2008 at 4:53 AM, lhein <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> currently I am reworking the servicemix-script component to have a jsr-223
> enabled endpoint.
> The JSR-223 is an abstraction layer for scripting for java. There are
> already engine implementations for lots of languages...for example groovy,
> javascript, jruby, bsh, xpath, xslt, velocity etc.
>
> A list of available engines can be found here:
> https://scripting.dev.java.net/
>
> In my opinion the old endpoint which uses Spring Dynamic Languages (there
> are only 3 languages supported by Spring) should be abandoned in 3.3
> Release. This old endpoint causes problems with dependency managment. Today
> I tried to get JRuby running on both old and new endpoint and figured out
> that this is impossible. The reason is, that JSR223 needs JRuby >=1.1 and
> Spring JRuby <=1.0....so what :)
>
> What do you think?
The subject of this message and the description above are opposing one
another here, so I'm a bit confused. As long as the following two
items are met:
1) You are refactoring the servicemix-script component to improve it's
ability to handle the various scripting engines and verisons, and
2) You are providing backward compatibility for the previous behavior
then I'm fine with a *refactor* of the existing servicemix-script SE.
I'm not in favor of abandoning (i.e., throwing away) the exisitng
servicemix-script SE. Please clarify further.
Bruce
--
perl -e 'print unpack("u30","D0G)[EMAIL
PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*"
);'
Apache ActiveMQ - http://activemq.org/
Apache Camel - http://activemq.org/camel/
Apache ServiceMix - http://servicemix.org/
Apache Geronimo - http://geronimo.apache.org/
Blog: http://bruceblog.org/
