The partial state transfer finds the Region by iterating, calling Fqn.toString() on the various regions and matching on that. Ugly, sure. And CacheSPI would need to expose an API to let that happen. It now exposes getEvictionRegionManager(), which I assume will be replaced. I've been asking myself why I'm arguing about this general area and proposing hacky solutions. It's because I don't see any reason why the JGroups partial state transfer API needs to limit the state id to type String. I think that will be changed someday. So I'm concerned about JBC building in all sorts of limitations based on it. IMHO what we should do is resolve why the JGroups API is limited to String and determine if and when that will change. Then decide what to do based on that knowledge. If based on that we decide to add in a few hacks to deal with the current API, I think that might be OK. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3984551#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...