Skip to content

Conversation

@nvasta
Copy link
Collaborator

@nvasta nvasta commented Jul 18, 2025

I'm almost done with SECOMLib for SECOM v2.0 and I added the new library in thsi latest version of the MSR.

This now theoretically supports both version of the SECOM API which you can also see in Swagger.

I haven't yet tested it very well but we can start to make sure everything looks OK.

In terms of changes, both SECOMLib versions had to be updated to support each other. Since this is a temp change, these are left as snapshots in the pom.

Apart from that, I added some OpenAPI configurations and some datetime formatters to deal with the various SECOM v1.0/v2.0 and MIR date formats. Also, one thing I don't like is the data product types which are locked to SECOMv1.0 but they are redefined in v2.0, so we kind of have to switch between the same enum from two libs...

Nikolaos Vastardis and others added 30 commits May 30, 2025 14:13
# Conflicts:
#	src/main/java/net/maritimeconnectivity/serviceregistry/controllers/InstanceController.java
# Conflicts:
#	src/main/java/net/maritimeconnectivity/serviceregistry/models/domain/Instance.java
Comment on lines +102 to +108
@Tag(name = "SECOM")
@Transactional
@Path(SEARCH_SERVICE_INTERFACE_PATH)
@POST
@Consumes(MediaType.APPLICATION_JSON)
@Produces(MediaType.APPLICATION_JSON)
public ResponseSearchObject searchService(@Valid SearchFilterObject searchFilterObject) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be possible to also have a GET version of this, as that is required by the specification?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants