don't assume replication is fired up during com.sap.sailing.server.test

This commit is contained in:
Axel Uhl
2020-04-28 18:40:33 +02:00
parent 7fa577ece4
commit 547a270bc1
@@ -4,12 +4,12 @@ import java.util.logging.Logger;
import org.apache.shiro.SecurityUtils;
import com.sap.sse.replication.FullyInitializedReplicableTracker;
import com.sap.sse.security.SecurityService;
import com.sap.sse.security.impl.Activator;
import com.sap.sse.security.impl.SecurityServiceImpl;
import com.sap.sse.security.userstore.mongodb.AccessControlStoreImpl;
import com.sap.sse.security.userstore.mongodb.UserStoreImpl;
import com.sap.sse.util.ServiceTrackerFactory;
public class SecurityBundleTestWrapper {
private static final Logger logger = Logger.getLogger(SecurityBundleTestWrapper.class.getName());
@@ -33,7 +33,7 @@ public class SecurityBundleTestWrapper {
new UserStoreImpl("defaultTenant"); // only to trigger bundle loading and activation so that security service can find the bundle and its original user store
logger.info("Setup for TaggingServiceTest in an OSGi environment");
// Note: This timeout of 3 minutes is just for debugging purposes and should not be used in production!
securityService = FullyInitializedReplicableTracker.createAndOpen(Activator.getContext(), SecurityService.class).getInitializedService(180 * 1000);
securityService = ServiceTrackerFactory.createAndOpen(Activator.getContext(), SecurityService.class).waitForService(180 * 1000);
}
return securityService;
}