Hi Alex, > Besides the obvious Java issues of dynamically loading code, > are there any > restlet-specific considerations for why you dynamically load an > Application instance from a jar file?
I'm not aware of specific issue. The design was aimed to support this scenario. > It seems to me that the Component instance in which the Application is > running is > protected from the Application instance. As such, there > isn't a way that the > dynamically loaded code could do something bad like call "stop()" on > the component > unless you made the component instance directly available in > the environment > somehow (e.g. as an attribute on the context). > > Am I correct? Are there other issues to consider? Yes, you are correct. Other potential issues are related to the client connectors which are shared between all applications. Starvation could occur if not care is used or thread are created without control. In the future, we would probably want to provide a stricter environment for application, similar to Servlet containers. Best regards, Jerome
