-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David
Esposito
Sent: Monday, June 18, 2001 8:36 AM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] ejbStore() delay seems to be a serious problem
-Original Message-
From: [EMAIL
Doesn't work??!! Are you sure you have the latest JBoss from
source? I put
this ejbStore on ejbFind in last week . Anyways, don't forget, ejbStore
will ONLY be called on entities of the same type of the finder
and that are
within the same transaction.
Sorry 'bout that ... I hadn't
PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David
Esposito
Sent: Monday, June 18, 2001 12:40 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] ejbStore() delay seems to be a serious problem
Doesn't work??!! Are you sure you have the latest JBoss from
source? I put
, June 18, 2001 12:40 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] ejbStore() delay seems to be a serious problem
Doesn't work??!! Are you sure you have the latest JBoss from
source? I put
this ejbStore on ejbFind in last week . Anyways, don't
forget, ejbStore
will ONLY be called
no responses.
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David
Esposito
Sent: Monday, June 18, 2001 1:16 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] ejbStore() delay seems to be a serious problem
My fault ... I forgot to copy
: Monday, June 18, 2001 1:16 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] ejbStore() delay seems to be a serious problem
My fault ... I forgot to copy the client lib directory over from the build
directory ...
Ok, so that seems to be a workaround ... Here's what I did:
Changed my
for me to document it?
-Dave
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On
Behalf Of David
Esposito
Sent: Monday, June 18, 2001 12:40 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] ejbStore() delay seems to be a
serious problem
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Aaron
Mulder
Sent: Monday, June 18, 2001 2:04 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] ejbStore() delay seems to be a serious problem
On Mon, 18 Jun 2001, Bill Burke wrote
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David
Jencks
Sent: Saturday, June 16, 2001 8:06 AM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] ejbStore() delay seems to be a serious problem
Hi,
A couple of comments
1. I think the worst
Of Scott
M Stark
Sent: Friday, June 15, 2001 12:38 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] ejbStore() delay seems to be a serious problem
Why is this a serious problem? The weblogic docs for the flag you mention
indicate the commit is still not done until the end
The behavior you'd get by setting that flag to false in weblogic would
also allow him to not break referential integrity in the case of his
transaction.
Scott M Stark wrote:
Why is this a serious problem? The weblogic docs for the flag you mention
indicate the commit is still not done until
]]
Sent: Friday, June 15, 2001 12:38 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] ejbStore() delay seems to be a serious problem
Why is this a serious problem? The weblogic docs for the flag you mention
indicate the commit is still not done until the end of the transaction and
that you
the bean will get what? Object does not exist when
they try to execute a method on the bean?
Cheers
-Original Message-
From: danch (Dan Christopherson) [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 15, 2001 1:38 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] ejbStore() delay seems
Christopherson)
Sent: Friday, June 15, 2001 1:38 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] ejbStore() delay seems to be a serious problem
He's not removing the modified bean: he's removing a bean that the
modified bean used to refer to. The issue is that the remove causes a
data
David Esposito wrote:
I am surprised that I am the only one that has raised this particular
example. It seems like it's something that people would do every day.
Actually it's far more common for people to complain about behavior
closer to what you want - Why is ejbStore being called so
Message-
From: David Esposito [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 15, 2001 1:30 PM
To: [EMAIL PROTECTED]
Subject: RE: [JBoss-dev] ejbStore() delay seems to be a serious problem
That's what I want ... I don't want the data to be committed, I just need it
to be visible by other operations
Hi,
Well, another possibility would be ketting your db vendor to check fk
constraints only on transaction boundaries, which would imho make the most
sense, however in the real world, Bill Burke just added (to cvs/2.3-2.4 I
think) some code that forces the container to store all modifications
...
-Dave
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of danch
(Dan Christopherson)
Sent: Friday, June 15, 2001 2:39 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] ejbStore() delay seems to be a serious problem
I think in this example, though
Actually Oracle will do this, are you using Oracle? You can change the
constraint checking to be deferred until commit.
-Original Message-
From: David Jencks [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 15, 2001 3:31 PM
To: [EMAIL PROTECTED]
Subject: Re: [JBoss-dev] ejbStore() delay
Hi all,
trying to sort that out.
David Esposito showed us a perfectly OK sequence of modifications
to some Entity beans within one TX. He reported problems with JBoss
accessing the DB while persisting, because of changed order of
modifications, creates/deletes seem to be done before updates,
20 matches
Mail list logo
