CamelContext tied to ThreadLocal instead of Activator instance -------------------------------------------------------------- Key: SWITCHYARD-251 URL: https://issues.jboss.org/browse/SWITCHYARD-251 Project: SwitchYard Issue Type: Bug Components: component-camel Affects Versions: 0.1 Reporter: Tom Fennelly Assignee: Daniel Bevenius Fix For: 0.2 Hey Dan... not sure if this was a hangover from an earlier day but atm, the CamelActivator ties the CamelContext to a ThreadLocal. There wouldn't appear to be a need to do this, assuming you want one CamelContext per deployment. You can just associated it with the activator instance itself, which is tied to the deployment instance. Tying it to the Thread doesn't work on AS7 since it seems to kick all deployments from the same Thread => meaning there'd only ever be one CamelContext instance created. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira