[resolved] Exception while calling MessagingEndpoint with talend:// scheme

[Anonymous]

Hi all.
After trying some of the examples mentioned within the TESB documentation, I am facing a new problem!
I created a simple sample job that displays a warning in the TESB console (tWARN via tLogCatcher and tLogRow). After deploying the job to our TESB instance, I created a sample route that should call this job (see attached images).
For the start of my route I used a Timer component that send out messages ervery 10 seconds. These Messages should be passed to the cTalendJob component. After investigating this procedure I realized that the cTalendJob component acts as a messaging endpoint (talend://<job_class>?<args>).
Seemed very easy so far. 😞 But the problems began as I started to deploy the route to our TESB instance via console with the osgi:install command.
The route could bei installed, but as soon as i started the route (via start <bundle_id>) I got the exception that the scheme talend:// wouldn't be recognized.
The exception I got was:
Failed to create route cMessagingEndpoint_1 at: >>> To <<< in route: Route] -> [To... because of Failed to resolve endpoint: talend://spappsesb.samplejob_0_1.SampleJob?context=Default due to: No component found with scheme: talend
Until now, I'm stuck looking for the bundle that contains the talend:// scheme definition or the cTalendJob component.
Maybe somebody could help me to figure out, what went wrong?
Thanks in advance.
Regards
Alexander

[Anonymous · Accepted solution]

Hello Alexander,
Yes, it's another issue . Apparently the older version of the camel-tis JAR file we delivered with the studio does not support that kind of context propagation. You could try to patch your studio so that it works, for that you need to find all files with name camel-tis-2.7.1.0.jar and replace the content of these files with that one:
http://dl.dropbox.com/u/218306/camel-tis-2.8.2.0.jar
Please make sure that you name your newly replaced files with the same name: 'camel-tis-2.7.1.0.jar'
After that you could try to re-run your sample, or just import mine:
Job called from Route which have a context parameter 'hasi': http://dl.dropbox.com/u/218306/JobCalledFromRoute.zip
Route that calls a job with context parameter 'hasi': http://dl.dropbox.com/u/218306/RouteCallsJob.zip
Renat