[ https://issues.apache.org/jira/browse/GEODE-4311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Anthony Baker resolved GEODE-4311. ---------------------------------- Resolution: Won't Fix > Hotdeploy jar merged into one classloader, muti-module hard to management > ------------------------------------------------------------------------- > > Key: GEODE-4311 > URL: https://issues.apache.org/jira/browse/GEODE-4311 > Project: Geode > Issue Type: Improvement > Components: configuration > Reporter: Dong Yang > Priority: Major > > Gemfire previous version have JarClassLoader for each deployed jar packages. > Then I can design my modules as hierarchical , there can have a core module > to save some internal status, sometimes it means a lot of meta informations. > But now , only one newest ClassPathLoader used for all deployed jar. Each > time you invoke the deploy command through gfsh , geode server-side will > rebuild the classloader and include all jars. It's simple than before, but i > lose all my meta informations even I have no code change for these part. > Just want to know what's the purpose for this change , Do I need implement my > own loader or these will be enhanced in future. -- This message was sent by Atlassian JIRA (v7.6.3#76005)