[
https://issues.apache.org/jira/browse/GEODE-8705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Udo Kohlmeyer updated GEODE-8705:
---------------------------------
Description:
Introduce Classloader isolation into Geode, to avoid the potential conflict of
custom code dependencies, from deploy jar, and the dependencies of the Geode
system.
This problem because evident when Geode was still dependent on Spring framework
4.3 and users wanted to deploy custom jars that used Spring framework 5. This
caused many library version conflicts.
This problem is not limited to the usage of Spring in the system but to ANY
dependent library that Geode and any potential custom jar would use.
The end goal is to have a system that is Classloader isolated and allows for
the usage of libraries of different versions within the Geode without any
conflicts.
See RFC
[https://cwiki.apache.org/confluence/display/GEODE/ClassLoader+Isolation] for
further details
was:
Introduce Classloader isolation into Geode, to avoid the potential conflict of
custom code dependencies, from deploy jar, and the dependencies of the Geode
system.
This problem because evident when Geode was still dependent on Spring framework
4.3 and users wanted to deploy custom jars that used Spring framework 5. This
caused many library version conflicts.
This problem is not limited to the usage of Spring in the system but to ANY
dependent library that Geode and any potential custom jar would use.
The end goal is to have a system that is Classloader isolated and allows for
the usage of libraries of different versions within the Geode without any
conflicts.
> Using JBoss Modules to implement classloader isolated jar deployment
> --------------------------------------------------------------------
>
> Key: GEODE-8705
> URL: https://issues.apache.org/jira/browse/GEODE-8705
> Project: Geode
> Issue Type: New Feature
> Reporter: Udo Kohlmeyer
> Assignee: Udo Kohlmeyer
> Priority: Major
> Labels: pull-request-available
>
> Introduce Classloader isolation into Geode, to avoid the potential conflict
> of custom code dependencies, from deploy jar, and the dependencies of the
> Geode system.
> This problem because evident when Geode was still dependent on Spring
> framework 4.3 and users wanted to deploy custom jars that used Spring
> framework 5. This caused many library version conflicts.
> This problem is not limited to the usage of Spring in the system but to ANY
> dependent library that Geode and any potential custom jar would use.
> The end goal is to have a system that is Classloader isolated and allows for
> the usage of libraries of different versions within the Geode without any
> conflicts.
>
> See RFC
> [https://cwiki.apache.org/confluence/display/GEODE/ClassLoader+Isolation] for
> further details
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
