No, you cannot have a value mapped to multiple keys such that when one mapping is removed, the other gets removed too. For an in-heap referential cache you could introduce state (or wrap) to represent the liveness of the value, and just check it outside. The mapping wouldn’t get removed, but since the mappings share the object they would both see the state mutation that marked the object as “removed”.
Regarding composite keys and/or regular expressions for keys you’ll have to be more explicit. What exact behavior would you be expecting?
--
You received this message because you are subscribed to the Google Groups "ehcache-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ehcache-user...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ehcache-users/2cc6c2e1-1c91-4415-9941-1e52839b686fn%40googlegroups.com.