Bertrand Delacretaz wrote: > On 10/31/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote: > >> ...One simple solution would >> be to have all script engines in microsling but make them optional.... >> ...The detection if the required stuff is available in the classpath could >> be done by just trying to instantiate the engine always. If >> instantiation fails, its not an error, but the engine is not available... > > That might be good enough, but you'd need a list of class names for > potential ScriptEngines, right? > > That list might be an init parameter for the MicroslingMainServlet, so > that people who need other scripting languages just need to add the > corresponding class names to that parameter, and make the engine > classes available. Ah, yes, we could have a default value for that parameter and if people really want to plugin their own one they have to provide this parameter. Yepp, simple and works.
> > We don't need to make scripting engines plugins super-easy in > microsling, I agree that such a mechanism would be sufficient, and > it's very easy to implement and understand. > Yepp, and the default impl comes with several engines, but we focus for the samples one one. Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
