Update Infomodel and Serializer about ids-messaging-services HOT 5 OPEN

Would imply the following constellation for Messaging-Services (see linked PR):

• bump infomodel-serializer from 4.2.8 to 5.0.3
• bump java from 4.2.7 to 5.0.3
• bump interaction from 4.2.7 to 5.0.3

From experience, there will also be breaking changes for the DSC and not just for the Messaging-Services itself, which will have to be tested and adressed in the run-up to the PR. So even if the PR in the Messaging-Services itself can be merged successfully, there could still be breaking conflicts in the DSC, which need to be evaluated beforehand before merging the linked PR.

from ids-messaging-services.

There are two main breaking changes compared to the DSC:

1. enum classes became interfaces with constants
2. the newly introduced UriOrModelClass

from ids-messaging-services.

@rmsoyta could you provide some more feedback on requirements from your side? Maybe we could find a version which does not lead to incompabilities but would satisfy your requirements.

from ids-messaging-services.

A short comment on that. Up to my current understanding, the breaking changes will be caused by the evolution of the version of the java classes (@tmberthold , @SebastianOpriel )? I think so because the serializer should be independent of the info model version used. It is included as test-dependency only and is (sadly) the sole target we test the serializer against. The changes in the interaction library (compared to the latest previous version) are marginal in the sense that we only updated the dependencies.

You could give it a trial and solely include the update of the serializer. This shouldn't cause breaking changes.

from ids-messaging-services.

We have updated the serializer in the DSC as a test, but the e2e-tests of the DSC fail, so changes are hiding here as well.
History of the failed test:
https://github.com/International-Data-Spaces-Association/DataspaceConnector/actions/runs/3629932830/jobs/6123853530

from ids-messaging-services.