Right now, all Ruby Verticles use the same classloading environment inherited from the container creation. This configuration is created by the first verticle deployment. So this does not support isolation groups and extra classpath entry.
Unfortunately, to support these, we would need to create a set of container, each one having its own configuration. We can introduce a Map<k, ScriptingContainer> where k is computed from the deployment classloader.
We would also need a way to stop container when the container is not used anymore (after undeployment).
Right now, all Ruby Verticles use the same classloading environment inherited from the container creation. This configuration is created by the first verticle deployment. So this does not support isolation groups and extra classpath entry.
Unfortunately, to support these, we would need to create a set of container, each one having its own configuration. We can introduce a Map<k, ScriptingContainer> where k is computed from the deployment classloader.
We would also need a way to stop container when the container is not used anymore (after undeployment).