Hi,
In that case it's ok for me.
Maybe ( just a suggestion ) we can add a flag in the new endpoint
configuration, for example ( backcompatible="true" )
that force the new endpoint to use the old names, for it's interaction
with the script, this flag could have false as default value so
where it's not present this means we don't need backward compatibility.
Another important feature for me is to ensure in the new component the
flag for copying attachments and properties.
Andrea
Lars Heinemann ha scritto:
Andrea,
the lightweight script component (this means ScriptComponent and
GroovyComponent) already use JSR-223 internally. So the switch for you will be
very easy. I will provide a migration guide later on.
The new endpoint will provide almost the same objects to the script as the lw
component did.
Lars
On Wednesday 11 June 2008 13:57:30 Andrea Zoppello wrote:
Hi Lars,
I've not understand if you're think to drop the
lightweight based component
"org.apache.servicemix.components.script.ScriptComponent" class,
or if you're only think to rework the standard servicemix-script component.
At the moment i'm still use the
"org.apache.servicemix.components.script.GroovyComponent" and
i'm very happy with it.
BTW but i've not found any examples on how to use servicemix-script in
the same way i use the GroovyComponent,
for example with the new servicemix-script it's possible to access the
exchange and the messages
inside the groovy script in the same way i'm doing now with the old one
component??
All this feature are important for me, so i could agree with you if the
new servicemix-script will give me all
the features of the old one.
An important feature coul be to mantain the same name of the variables
used by the old component so that the
old script will be reusable.
Andrea
Lars Heinemann ha scritto:
Additional info for Spring Dynamic Language Support:
http://static.springframework.org/spring/docs/2.5.x/reference/dynamic-
language.html
Lars
On Wednesday 11 June 2008 12:53:21 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
