On 3/13/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
<snip/>
Also, what is "a more dynamic invocation mechanism"? Most scripting languages out there use dynamic typing - or duck typing for Ruby :) - and do not define interfaces and method signatures. Going further Ruby for example defines a method_missing method that will be invoked if the target component does not implement the method a client is trying to invoke. I think that an SCA runtime assembled to run scripting components will have to support that. Ant may have more insight here as he's been doing some scripting integration work with the Java runtime.
Yes I'd really like to get the script components working in a more dynamic way. Other script languages besides Ruby also support 'method missing' type function, Rhino will in their up coming release, many other dynamic languages support things like defining new functions or methods at runtime. For these dynamic languages having to define type information via annotations or side files is unnatural, so I'd like to get to where they're not mandatory. Maybe enable script components to be wired up anywhere and the invocation is just attempted and fails at runtime if the function doesn't exist or the argument types are not what the script expects. Along with getting the Axis2 binding going again in the trunk I also plan to get the script container going again as well and explore some of these things. I have tried in the past but its been difficult to get to work, it looks like some of the recent spec and trunk changes may make some of this easier to do now. ...ant
