Open oleotiger opened 6 years ago
I thing you're right about that @oleotiger.
But what's the best way to fix this? I'm afraid extra .clone()
won't cut it either; merely pushing the problem one step further (if at all, depending how well the method is implemented). Should we simply add warning to the documentation about shallow copies of properties?
In
Message.java
, the functionvoid copyFrom(Message m)
copiespropeties
asif (m.properties != null) { Set<String> keys = m.properties.keySet(); for (String key : keys) { updateProperty(key, m.getProperty(key)); } }
which add a reference topropeties
of the original message instead of a clone of it when a property is such asList<Integer>
.