You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should provide a mock implementation of the VersionService interface in the mock-connector runtime.
WHY
With the update to edc 0.11.0-20241213-SNAPSHOT, the protocol api was excluded from the mock-connector runtime since no mock provider was implemented for the VersionService. If we want to keep the protocol api available for mocking, we have to provide an implementation for it.
The text was updated successfully, but these errors were encountered:
In the mock-connector runtime and a implementation stub (similar to existing ones) for VersionProtocolService that implements both AbstractServiceStub and VersionProtocolService. Something similar to the next.
public class VersionProtocolServiceStub extends AbstractServiceStub implements VersionProtocolService {
public VersionProtocolServiceStub(ResponseQueue responseQueue) {
super(responseQueue);
}
@Override
public ServiceResult<ProtocolVersions> getAll(TokenRepresentation tokenRepresentation) {
return responseQueue.getNext(ProtocolVersions.class, "Error retrieving ProtocolVersions: %s");
}
}
and in the MockServiceExtension provide the new VersionProtocolServiceStub similar to the ones already provided.
The exclusion of the protocol api can be now removed.
WHAT
We should provide a mock implementation of the VersionService interface in the mock-connector runtime.
WHY
With the update to edc 0.11.0-20241213-SNAPSHOT, the protocol api was excluded from the mock-connector runtime since no mock provider was implemented for the VersionService. If we want to keep the protocol api available for mocking, we have to provide an implementation for it.
The text was updated successfully, but these errors were encountered: