{"push_id":792664852,"size":1,"distinct_size":1,"ref":"refs/heads/HWKBTM-162","head":"f3bcc0e6beeba63aa2d8c42eb40c3ca0868b5680","before":"f065ddf838efdc616e835f52403137775f3234aa","commits":[{"sha":"f3bcc0e6beeba63aa2d8c42eb40c3ca0868b5680","author":{"email":"f9023000f29773649f3850298becb9544b5fd6a9@brownuk.com","name":"Gary Brown"},"message":"HWKBTM-162 Instrument a camel/cxf based webservice example with two interacting services. When running in Wildfly, this required an additional Apache CXF instrumentation rule, for when integrating with Jetty, as the servlet instrumentation rules did not trigger, and instead an internal integration with Jetty was used.\n\nHWKBTM-165 Introduce mechanism for general correlation - this subsumes the previous link mechanism which is a 'one time use' correlation between two instrumentation rules. This was required to handle the execution of separate camel components, within a route, in different threads. Further work may be required, specifically including other concurrency constructs in camel, to find the most general solution.","distinct":true,"url":"https://api.github.com/repos/objectiser/hawkular-btm/commits/f3bcc0e6beeba63aa2d8c42eb40c3ca0868b5680"}]}