Any specific bits as potential candidates?
I was basically thinking all of them; for anything used by PojoCache we could add a getter/setter. I think Ben is going to use delegation in PojoCache instead of subclassing, so maybe it's good to wait until he's done that so we don't add getter/setters for fields he won't need after his refactor.
This came up because I'm creating a StateTransferManager for JBCACHE-465 so Ben can do what he wants with a PojoCache-specific version. I was adding the field for it and didn't want to add another protected field :)
+1 here since we are moving to API/SPI model.
For PojoCache integration, I have refactored my code to use some delegation (from a sub-class of TreeCache). So next step is to use Cache implementation directly. There is an integration task for this in 2.0.
I think it is ok to go ahead now. I suspect there are only few in PojoTreeCache that needs changed (without looking at it first).
+1 on removing any protected fields. They should all be private with getter/setters where necessary.