Add support for data provider capabilities in server and InAndOut analysis

[bhufmann]

• trace-server: serialize IDataProviderCapabilities in descriptors
• Set Capabilities in relevant descriptors of InAndOutDataProviderFactory

Requires eclipse-tracecompass/org.eclipse.tracecompass#198 to be integrated.

see also eclipse-cdt-cloud/theia-trace-extension#1158

Signed-off-by: Bernd Hufmann [email protected]

[PatrickTasse]

Would this be the same as using writeObjectField on the capabilities?
The difference could be that we are fixing the capabilities to serialize even if new ones are added to the class.

[bhufmann]

The method getCapabilities returns an instance of IDataProviderCapabilities, but it doesn't guarantee that it is DataProviderCapabilities object which has 2 boolean fields canDelete and canCreate. It could be just an anonymous class that returns hardcoded values for methods canDelete and canCreate. For that case, the serialization would cause an exception. To rely on writeObjectField we would have to have jackson annotated classes. Not sure if it would work if the annotation is on the interface methods.

Besides, we have not added the jackson dependency to Trace Compass core for that, because our stand was that the TSP client to trace server interface is not the same than the trace server to Trace Compass core interface, where the latter is the Trace Compass interface, that is also used in classic Trace Compass. If we had started without the legacy code and the TSP as main interface, then we probably would have done it differently.

[bhufmann]

Note, it would be possible to re-visit how internal data structures are serialized in over the TSP using jackson annotation. But that should be a separate task for all TSP data structures.