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
is this behaviour a design rule?. I would like to use the real loader in test scope. For instance, I tried to run a test with kvs in memory but kvs library uses this library which by default load the mockEngine if it's on classpath threfore I couldn't connect to the kvs. Would you accept a PR for adding this feature?
This is the current code that I mention (Engine.java):
@SuppressWarnings("rawtypes")
private static void loadEngine() {
for (Builder b : builderLoader) {
if (b instanceof MockBuilder) {
builder = b;
break;
}
if (builder != null) throw new IllegalStateException("Many Rest Clients implementations found");
builder = b;
}
loadCallbackFactory();
}
@SuppressWarnings("rawtypes")
private static void loadCallbackFactory() {
for (CallbackProcessor f : callbackLoader) {
if (f instanceof MockCallbackProcessor) {
callbackProcessor = f;
break;
}
if (callbackProcessor != null) throw new IllegalStateException("Many Rest Clients implementations found");
callbackProcessor = f;
}
}
The text was updated successfully, but these errors were encountered:
mbussoMeli
changed the title
loadEngine uses mockEngine by default if it's on classpath
LoadEngine uses mockEngine by default if it's on classpath
Nov 27, 2019
is this behaviour a design rule?. I would like to use the real loader in test scope. For instance, I tried to run a test with kvs in memory but kvs library uses this library which by default load the mockEngine if it's on classpath threfore I couldn't connect to the kvs. Would you accept a PR for adding this feature?
This is the current code that I mention (Engine.java):
The text was updated successfully, but these errors were encountered: