[
https://issues.apache.org/jira/browse/APEXCORE-767?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16113595#comment-16113595
]
Vlad Rozov commented on APEXCORE-767:
-------------------------------------
Why not to set {{initialClassLoader}} along with the {{loaderThread}} on the
first call to {{loadDependencies()}}? While Beam Runner does not use it now,
the use case I mentioned is easy to support, so other runners/launchers may use
it.
> Duplicate class loading in CLI for single application launch
> -------------------------------------------------------------
>
> Key: APEXCORE-767
> URL: https://issues.apache.org/jira/browse/APEXCORE-767
> Project: Apache Apex Core
> Issue Type: Bug
> Reporter: Thomas Weise
> Assignee: Florian Schmidt
>
> StramAppLauncher will create multiple class loaders in a way that leads to
> duplicate loading of the same class (while listing app package, then when
> launching). It also appears that the context class loader is never reset.
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
