Further Talend integration

[mdutoo]

• bugs : solved by Talend, still TODO Open Wide update Talend demo next time we work on it

  • 46 Incomplete WSDL - Talend airport tutorial

  • in tXMLMap, inner join lookup rejects are not emitted. Sample uploaded by JGuillemotte (see below).
• TALEND Question to improve Talend ESB job packaging : we've done an "export" in the Studio, can it be done better, ex. by having a single Talend ESB runtime for all exported jobs ?
• monitoring : Open Wide share architecture with Jasmine probes, Talend point to committed CXF interceptors
• runtime discovery : let Talend ESB runtime tell EasySOA about services it runs, ex. using OSGi or CXF configuration (just as done with FraSCAti in #28)
• Make EasySOA Registry's known services available in Talend Studio
  • by filling its job Metadata, palette or with a new Repository concept and connector. This can be done through REST interactions with EasySOA model (alternatives include making this API closer to known standards : SOAML, UDDI...)
• Use Talend to make existing services less complex (see #58 EasySOA Light - Further scaffolding features)
  • by designing a Talend transformation between two service schemas gotten from EasySOA. This requires having easy access to both service schema in Talend Studio, ex. through service repository as said above, or by initializing the job design with them.
  • and running it in Talend ESB. This implies making Talend ESB a supported runtime of EasySOA i.e. has a mapping from (at least a part of) the EasySOA model. An alternative is running it as an EasySOA proxy on FraSCAti (defined in #59 Scaling up FraSCAti proxies).
• Make a Service repository out of EasySOA Registry, by using Talend, EasiFab and Light use cases to define a common development cycle, its model and API on top of EasySOA Registry, contribute it to Eclipse (at least the API, possibly an Apricot-based implementation when Nuxeo DM switches to it)
  • on the Talend side, a first step : store in Talend WSDL metadata for each service endpoints for all environments, and let the environment be chosen at deployment, ex. like Talend environment properties

[JGuillemotte]

Add two jobs in Talend tuorial project : https://github.com/easysoa/EasySOA/tree/master/samples/Talend-Airport-Service/Talend-Airport-Service-Tutorial

• First job : SimpleProvider_xpathError to show a xPath error generated by the job, unknow reason.
• Second job : SimpleProvider_errorRejectsNotEmitted to show the problem of inner join lookup rejects not emitted by tXMLMap component.

These examples work with the simpleConsumer job.