TRS base is empty

[dhakehurst]

Hi,
(this is a very useful project by the way, thanks)

I am adding test data using the client-toolchain,
however, the trs/base seems to be empty.

according to Copilot's analysis:

The TRS is correctly registered and resource changes are tracked via trsEventHandler.onCreated() calls in RestDelegate. However, when server starts, RestDelegate maps are empty, so TRS initializes with zero resources. Once client-toolchain populates data via POST requests, new resources ARE added to TRS correctly. The fix is to make TRS initialization lazy or ensure it re-syncs after the maps are populated.

I am still too new to the code base to be sure if this is correct, but it looks like a reasonable assesment.

What am I missing?
many thanks

[Jad-el-khoury]

@dhakehurst Can I suggest we take dialog on the OSLC forum https://forum.open-services.net/?

In the meantime, here's a quick answer ...
If you are familiar with TRS, there is a baseLog and and changeLog. In this case, the BaseLog is empty. All changes (via POST) will be handled in the ChangeLog.

[berezovskyi]

An empty TRS base should be fine. I do not recall the spec requiring it. I do not believe this to be a bug. Unless you can produce some log with Jazz complaining about it? You should have some TRS feed validation tools in JTS.

If you are trying to build your own TRS consumer (eg a tiny "LQE" prototype), you might want to try eclipse-lyo/lyo#873 . To be clear, I do not think this is your case (yet?).

[berezovskyi]

Marking invalid for now but keeping it open until we get to the root cause of your TRS issues with Jazz.