Comment from Pinaki in an email about r828880 -
1. introduces a JPAProperties class. It is in preliminary stage but its purpose is to corral all JPA property key/value manipulation. If you are playing with JPA properties and needs more support, please consider adding them to this class rather than spreading them.
2. Or know of some related processing happening elsewhere please consider relocation. For example, I found the following logic tucked in FetchPlanHintHandler...which may now live in JPAProperties.
// to accomodate alias name input in relationship with enum values
// e.g. "optimistic-force-increment" ==
String strValue = ((String) value).toUpperCase().replace('-', '_');
3. Changed use of implementation to interfaces in HintHandler. Please note that implementations are preferred not only for architectural aesthetics or programming discipline, but also helps any other downstream plug-ins.
4. Used FetchPlan to carry these cache mode properties from facade to kernel. This decision aligns better with other configuration properties such as lock modes etc, and also tagging them on FetchPlan helps to reuse tested pathways. This change deprecated supporting methods/constructs appearing in StoreContext.