2015-11-04 15:16 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com>:
> Yes, and would avoid a custom configurator :). > > In way the difficulty is that the configurator takes over the instance creation, but doesn't care about its destruction. If the default Tomcat configurator took care of newInstance, the tracking would fail if the configurator is replaced. Not very good. So the InstanceManager.newInstance(Object o) should always be used instead IMO after delegating instance creation to whatever configurator is present. Maybe from WsSession (since it's in a good position to call destroyInstance as well). Rémy
