If it could pan out that BSF works; that would be a awesome! Following this thread there are several preferences of languages. Javascript is my preference for scripting (as mentioned by Matt below it could then be the plug-in developer's choice as to the language.)
BSF seems to support the following: javascript, jacl, netrexx, java, javaclass, bml, vbscript, jscript, perlscript, perl, jpython, jython, lotusscript, xslt, pnuts, beanbasic, beanshell, ruby, judoscript, groovy I don't see a jelly engine though :\ Aside note: We're using BSF in a call center application. It's hard to explain to scripting developers that when they call a method on a java object we've exposed to the framework that they're getting back java objects.. For example a java String not a javascript String and that they need to cast it back somehow - like this; var myString = javaObject.returnsAString() // myString has the java.lang.String method length(): myString.length() // and throws an error on javscript: myString.length var myString = "" + javaObject.returnsAString() // casts it back to javascript String // so myString.length is ok as the javascriptor expects > -----Original Message----- > From: __matthewHawthorne [mailto:[EMAIL PROTECTED] > Sent: Friday, January 09, 2004 9:24 PM > To: Maven Users List > Subject: Re: Simple properties question... [...] > Jason, do you have any thoughts on using something like BSF for the > plugins? That way, if I'm understanding things correctly, the actual > plugin implementations could be written in a scripting language of > choice. [...] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
