Andrew, could you create a simple testcase, please? Taking into account
the description you gave, it shouldn't be hard to do.
Thank you,
alex
Andrew May wrote:
The Entity beans only have local interfaces. They are accessed via a
Stateless Session bean which has transaction=Required for all me
The Entity beans only have local interfaces. They are accessed via a Stateless Session
bean which has transaction=Required for all methods. The only non-standard thing is that
the get* methods are marked read-only in jboss.xml.
Where I'm performing a delete it's a simple call to the session bean
Are there other beans involved in the tx? Something, causes
synchronization. If all the CMP2 beans have sync-on-commit-only=true,
then it shouldn't happen.
alex
Andrew May wrote:
Alex,
Thanks for your reply - my answers in-lined:
-Andrew
Alexey Loubyansky wrote:
Hello, Andrew.
my comments
Alex,
Thanks for your reply - my answers in-lined:
-Andrew
Alexey Loubyansky wrote:
Hello, Andrew.
my comments in-lined.
Andrew May wrote:
I'm having a problem trying to user sync-on-commit-only and
cascade-delete with JBoss 3.2.1 (Sun JDK1.4.2, Solaris).
We've got a number of related entit
Hello, Andrew.
my comments in-lined.
Andrew May wrote:
I'm having a problem trying to user sync-on-commit-only and
cascade-delete with JBoss 3.2.1 (Sun JDK1.4.2, Solaris).
We've got a number of related entities like this:
LOGIN---IDENTITY
| |
LOGINPROPERTIES
On Thursday, July 10, 2003, at 19:23, Jeremy Boynes wrote:
This causes the container to flush e.g. before executing finders, which
is required (and often desired) behaviour. Setting this to true will
mean finders will not be aware of any modifications already made in the
transaction. I'd recommend
lt;[EMAIL PROTECTED]>
Sent: Thursday, July 10, 2003 6:23 PM
Subject: RE: [JBoss-user] sync-on-commit-only
> This causes the container to flush e.g. before executing finders, which
> is required (and often desired) behaviour. Setting this to true will
> mean finders will not be aware of
This causes the container to flush e.g. before executing finders, which
is required (and often desired) behaviour. Setting this to true will
mean finders will not be aware of any modifications already made in the
transaction. I'd recommend leaving it at false unless you know that your
application c
