On 10/31/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote: > ...Which plugin mechanism do you suggest?...
I think we have two options at this point, I'll summarize here and wait a bit in case more people want to make suggestions. 1) Our own simple "jar service provider" mechanism microsling looks for jar files providing a file like [1] , using our own simple ServiceLoader class (like Felix suggests, that's about 10 lines of code). This is my favorite for now, it's clean and simple to implement, and we can prepare ready-to-drop jar files of the ScriptEngines, which can be OSGi bundles as well, for Sling OSGi. 2) List of script engine class names as a MicroslingMainServlet init parameter microsling tries to load each engine, and if that fails forgets about that engine. Adding more engines is a bit less practical as one needs to edit web.xml. [1] https://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-core/src/main/resources/META-INF/services/org.apache.jackrabbit.core.query.QueryTreeBuilder
