I just went ahead and did the same we do for the other modules.
On Tue, Dec 12, 2017 at 9:47 PM Steve Ebersole wrote:
> Vlad, these changes cause some failures in the userguide tests[1]. This
> is not completely unexpected since they seem to do caching-specific
> assertions. However, for the l
Vlad, these changes cause some failures in the userguide tests[1]. This is
not completely unexpected since they seem to do caching-specific
assertions. However, for the life of me I cannot figure out how to run
these locally. The problem is the annotation processor for generating the
"JPA static
I have just pushed this work to the 5.3 branch. Tomorrow I will start
working on getting this all integrated with master (and branching 5.2
off). At that point we are pretty much ready for that first Beta, so let
me know if anyone notices anything awry - this is a pretty big change.
On Tue, Dec
We discussed this further in chat. For the sake of others reading, the
summary: I got confused about the risks of having multiple cache
regions for a single hierarchy; the proposal is *not* to have multiple
regions yet be able to exclude specific types from the (shared) region
of a type hierarchy.
And btw, this *has* to happen. JPA requires it and the 2.2 TCK tests for
it. So there is no "keep allowing caching at the root-level" option here
On Tue, Dec 12, 2017 at 12:44 PM Steve Ebersole wrote:
> Its not any different than `#get( LegalEntity.class, key )` in the old
> config when key r
Its not any different than `#get( LegalEntity.class, key )` in the old
config when key refers to a Person and Person is *not* in the cache simply
because it has not been loaded/saved via this SF.
On Tue, Dec 12, 2017 at 12:33 PM Sanne Grinovero
wrote:
> Conceptually it sounds useful but I'm wond
Conceptually it sounds useful but I'm wondering about this being safe
to do in various more tricky mapping scenarios.
For example consider this case:
@Inheritance(...)
@Cache(...)
@Cacheable(true)
class LegalEntity {
...
}
@Cacheable(false)
class Person extends LegalEntity {
...
}
@Cach
HHH-12146 is about being able to enable/disable caching at various levels
in an entity hierarchy. E.g., given a hierarchy such as `Person` and
`Company` both extending `LegalEntity`, this would allow users to say that
only `Company` should be cached but not `Person` nor any other
`LegalEntity` sub
