From do-not-reply at jboss.com Wed Jan 31 09:37:07 2007 Content-Type: multipart/mixed; boundary="===============8560928059269278182==" MIME-Version: 1.0 From: estaub To: jboss-dev-forums at lists.jboss.org Subject: [jboss-dev-forums] [Design of JBoss jBPM] - Support for Bean Scripting Framework (BSF) Date: Wed, 31 Jan 2007 09:37:07 -0500 Message-ID: <31998199.1170254227351.JavaMail.jboss@colo-br-02.atl.jboss.com> --===============8560928059269278182== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable I'm planning to implement support for BSF and will contribute it back if it= 's wanted. = (BSF supports pluggable scripting engines and pluggable domain classes.) = I'm posting this here, rather than on the forum, to make sure we don't end = up with duplicate efforts. = If this was the wrong thing to do, apologies in advance. = My current plans are to just provide a way to configure a global scripting = engine via jbpm.cfg.xml. In the future, it would be desirable to make this = settable in the Process Definition. = I'll make sure this works with BeanShell and Groovy - other folks will have= to vet Rhino, etc. = Current estimate is "before end of February". = Any thoughts? Requests? Is this useful to others? I haven't seen much about= it on the forums. = This was originally misposted on JIRA as http://jira.jboss.com/jira/browse/= JBPM-830. Tom Baeyens responded there: anonymous wrote : good idea. i mainly would be interested to know how you c= ould enhance the current scripting support to BSF without braking backwards= compatibility. = | = | if this could be done with adding a language attribute to the script ta= g that has the default value of 'bsh', I'm all ears :-) = Backward compatibility is certainly a requirement. As for "how", it superf= icially looks easy; I'll know more shortly. A