java/com.sap.sse.common/src/com/sap/sse/common/impl/RenamableImpl.java
... ...
@@ -25,5 +25,4 @@ public class RenamableImpl implements Renamable {
25 25
public void setName(String newName) {
26 26
this.name = newName;
27 27
}
28
-
29 28
}
java/com.sap.sse.security/src/com/sap/sse/security/impl/SecurityServiceInitialLoadExtensionsDTO.java
... ...
@@ -16,7 +16,7 @@ import com.sap.sse.security.shared.impl.LockingAndBanning;
16 16
* initial load format can be added to this DTO type. The benefit, compared to adding new content with
17 17
* explicit {@link ObjectOutputStream#writeObject(Object)} and {@link ObjectInputStream#readObject()} calls,
18 18
* is that there is a certain built-in backward compatibility when a replica with a new version and additional
19
- * fields expected in the initial load tries to replica from an older version where those fields don't exist
19
+ * fields expected in the initial load tries to replicate from an older version where those fields don't exist
20 20
* yet in this type. Then, those additional fields will come out as {@code null} on the replica, and the replica
21 21
* at least has a chance to continue with a useful initialization of those data structures instead of having
22 22
* the replication of {@link SecurityService} and all subsequent {@link Replicable}s fail due to incompatible