Right - it sounds like something the platform+engine should be sorting out before starting the workflow.
On 6 March 2015 at 16:58, alaninmcr <[email protected]> wrote: > On 06/03/2015 16:38, Stian Soiland-Reyes wrote: >> >> Never mind the logic question.. I Was looking at >> >> >> https://github.com/apache/incubator-taverna-common-activities/blob/master/taverna-beanshell-activity/src/main/java/net/sf/taverna/t2/activities/dependencyactivity/AbstractAsynchronousDependencyActivity.java#L267 >> >> ..which seems to build a big dependency list for every dependency >> activity in the workflow - even if the classloader sharing is not set >> to "workflow". But the only other option now in the enum is "system" >> which would still cover the whole workflow. > > > Yes. That code almost certainly should be replaced - especially as it is not > clear how (if?) it will work with OSGi. > > It caused problems with the components and trying to ensure that they worked > correctly where the component's realizing workflow (directly or indirectly) > contained a beanshell with dependencies. > > Alan > -- Stian Soiland-Reyes Apache Taverna (incubating) http://orcid.org/0000-0001-9842-9718
