Am 2020-04-17 um 09:22 schrieb Alan Bateman:
On 16/04/2020 11:05, Osipov, Michael wrote:
That's exactly the point. I don't want to bundle it with the webapp,
but with Tomcat only for all webapps. It will be added to
CATALINA_HOME/lib along with a custom realm. Both are loaded with
On 16/04/2020 11:05, Osipov, Michael wrote:
That's exactly the point. I don't want to bundle it with the webapp,
but with Tomcat only for all webapps. It will be added to
CATALINA_HOME/lib along with a custom realm. Both are loaded with
Tomcat's common.loader [1]. No, it does not load from
Am 2020-04-16 um 11:46 schrieb Alan Bateman:
On 16/04/2020 09:46, Osipov, Michael wrote:
Folks,
can some one, or Rob, explain why this class is explicitly tied to the
application class loader [1] when using the ServiceLoader? Is there
any specific implication when the thread context class
On 16/04/2020 09:46, Osipov, Michael wrote:
Folks,
can some one, or Rob, explain why this class is explicitly tied to the
application class loader [1] when using the ServiceLoader? Is there
any specific implication when the thread context class loader is used?
This makes it rather
Folks,
can some one, or Rob, explain why this class is explicitly tied to the
application class loader [1] when using the ServiceLoader? Is there any
specific implication when the thread context class loader is used?
This makes it rather problematic using in a stacked class loader
