> 1) Our own simple "jar service provider" mechanism > 2) List of script engine class names as a MicroslingMainServlet init parameter
maybe thats a stupid idea and i am not sure if i even want to bring up this option ;) : (3) how about using the workspace itself as an extension mechanism... something like: /.microsling/script-engines/esp /.microsling/script-engines/fm /.microsling/script-engines/rb ... which would host all the mapping information also allow for dynamic extension and distribution/installation as a content package. regards, david
