Hey Rickard,
> Hi!
>
> "Bordet, Simone" wrote:
> > I will repost here a question that Ole issued some time
> ago, that is now
> > under my fingers. I've gone through the specs, but haven't
> found nothing
> > related.
> >
> > If I have a call to an Entity Bean with *no* transaction,
> and another call
> > for the same bean with a transaction is issued by another
> client, current
> > implementation will run concurrently these calls (while the
> opposite case,
> > first a call with tx and then the one with no tx makes the
> second one
> > waiting).
> >
> > The question is if I should make the second call (the one
> with tx) wait.
> >
> > And what about 2 (or more) concurrent calls both with no tx
> associated (run
> > concurrently or let the second wait) ?
>
> Is this really the current case? If so it is terrible, and quite
> astonishing! I am quite certain that the previous cache did not allow
> this, so this must be a recent error.
Pah! Forget about all the above, I was working on a incomplete
EntityInstanceInterceptor, probably I deleted a slice of code by mistake.
Sorry for the noise, it is of course all OK.
Simon
