I have developed a route named "LookupAdapater" that is listening on a JMS queue for request to do a lookup of data in the database. The route calls a job named "Lookup" that does the actual query of the lookup. I published the route to the artifact repository, but the "LookupAdapter-feature" node in Nexus Artifact Repository only contains the route, not the job, the job is in its own node "LookupAdapter_Lookup" (it also has the node "LookupAdapter"). Then I created a deployment task in TAC (under "ESB Conductor"), by selecting the only available "LookupAdapter-feature". When deploying, it says one of the bundle is "not active" or something like that, I suspect it is talking the the job "Lookup", also, in the "Config Properties" tab, I only see the context values used by the route "LookupAdapter", not seeing those used by the job "Lookup". What did I do wrong and is there way to publish the route and job as one unit?
