"EJB 3.0 Persistence 5.6.3" wrote:
Propagation of persistence contexts only applies within a local environment. Persistence contexts are not propagated to remote tiers.
So propagation will not occur if the call is really remote. Calling locally through a remote interface will propagate the PC.
I see ... so I would say it's a hole in the specs ;)
If I use a bean via its remote interface, I think where the bean is deployed should be really completely transparent to the programmer - and it isn't as it matters if the beans are deployed together or not. (The code may execute differently if the PC is propagated or not)
To simulate remote behaviour you can put remote interfaces in additional ear and configure isolation for this ear (default is local).
I found additional situation: attribute mappedName, it is a pity that semantics of global name resource (global in some context) is not standardised.