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
When debugging caching issues, I stumbled upon TransactionalCache line 419. There, CacheRegionKeys are filtered out and their underlying key values should be returned. When executing the method I still got keys of a class "CacheRegionKey".
Both classes have the same serialVersionUID = -213050301938804468L and the same attributes in the same order, so I suspect this is an errror. The sub class has two additional get-methods, so it looks like there was a merge-conflict, where one branch moved the class into a new file and another branch added these methods and during merge it was decided to keep both classes, instead of moving the new methods to the moved class.
The text was updated successfully, but these errors were encountered:
When debugging caching issues, I stumbled upon TransactionalCache line 419. There, CacheRegionKeys are filtered out and their underlying key values should be returned. When executing the method I still got keys of a class "CacheRegionKey".
It turns out, there are 2 classes CacheRegionKey: One as a sub class of TranasactionalCache and one is a standalone class. The sub class is older being introduced with 4.0 while the standalone class was introduced in 4.2.
Both classes have the same serialVersionUID = -213050301938804468L and the same attributes in the same order, so I suspect this is an errror. The sub class has two additional get-methods, so it looks like there was a merge-conflict, where one branch moved the class into a new file and another branch added these methods and during merge it was decided to keep both classes, instead of moving the new methods to the moved class.
The text was updated successfully, but these errors were encountered: