> I dont understand why in a read only cache ( what Christoph is trying to
> achieve) you need a transaction aware distributed caching.
For a read-only cache, we can just use a JCS distributed cache.
P.S. in my discussions of LockServers, I assumed that everyone would
realise that the LockServer
Hi all...
I'm having a little problem trying to map my objects. My mapping looks
like this:
The db looks like this:
create table Foo ( fooId bigint not null primary key, discriminator
bigint not null, name varchar(256) )
create table FooBar (fooB
I like the idea of making it more consistent. That will make it easier to
use.
I personally would vote for defaulting cascade-to-save to null since I don't
use primitives as ids. It might be worth finding out how many folks use
primitives vs. objects as ids before choosing a default.
Regards,
J
> (3) After fielding so much user confusion over the semantics of cascade
> ="all", I found a way to extend the functionality consistent with the
> current semantics and (hopefully) without any risk of breaking existing
> code. I will need some feedback about the details here, though:
>
> There are
