|Re: [recommenders-dev] Enabling Error Reporting in TACIT|
Sorry, I canât answer that without trying myself.
You certainly do not need implement everything from scratch. There are quite a few classes you could reuse (like the local history classes, all the filters & predicates, Status to ErrorReport transformations, the actual IO class etc.) But when it comes to the workflow, we rely on DI and EventBus interfaces which are not available in E3. AERI also uses require-bundles and import package directives you may not be able to satisfy satisfy in your E3 RCP app. Thus, at some stage you may ending up copying and modifying AERI code into your own bundle.
Iâm sorry. Iâm not able to help you more than with that ATM. Iâve no plans to write an E3 compatible client for you :-)
If you go the extra milage, you could consider to refactor the necessary parts and contribute it to the open source project so that others can reuse it.
The knowledge transfer company
Robert-Bosch-Str. 7, 64293 Darmstadt
Managing Director: Dr. Marcel Bruch
Handelsregister: Darmstadt HRB 91940