Sounds great, if you need help refactoring Shawn and I can lend a hand. Paddy Sent via BlackBerry from T-Mobile
-----Original Message----- From: Felix Meschberger <[EMAIL PROTECTED]> Date: Tue, 20 Nov 2007 11:38:57 To:Sling Developers <[email protected]> Subject: Scripting Engine Support Hi all, In Sling we currently have the ScriptEngine interface to support multiple scriping engines. Implementations exist for JavaScript (Rhino), Velocity, Ruby, Freemarker and JSP. I proposed this light-weight interface because, I want to go forward quickly and didn't want to lock in to any of the other two big contenders in the field: Java Scripting (JSR-223) and BSF. I now learned that BSF 3 (currently in Beta) will be an implementation of the Java Scripting API and will be ready to run in Java 1.4 and newer (as opposed to Sun's reference implementation, which is part of Java 6 and not available earlier). So this opens the question again, whether we really need our own interface for scripting engines. I suggest we drop the ScriptEngine interface in favore of using Java Scripting. We could then make use of all Java Scripting supporting scripting languages and would not have to implement our own bindings. WDYT ? Regards Felix
