The JSR-223 logic will be put to a new service engine called "servicemix-scripting". I would like to deprecate the servicemix-script in favor for this new SE.
I will commit the changes on thursday. I already reverted all changes made to servicemix-script. The new SE will be a replacement for the LW script / groovy component as well. I will put on a component wiki and a migration guide in the next days. Regards Lars lhein 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? > > Regards > Lars > > -- View this message in context: http://www.nabble.com/-DISCUSS--Abandon-old-servicemix-script-endpoint-tp17774828p17788710.html Sent from the ServiceMix - Dev mailing list archive at Nabble.com.
