Re: [JBoss-user] Keeping cmp beans in synch

2001-06-28 Thread Allen fogleson

Do you remove it by calling the database or the remove() of the entity bean?
if the former... look at your default standardjboss.xml and change the
commit option from the default of A. This presumes that the ejb has
exclusive access to the database. you want either B (caching but non
exclusive access) or C (non caching state loaded at the beginning of each
transaction)

al

- Original Message -
From: Chris Tragas [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, June 28, 2001 1:06 AM
Subject: [JBoss-user] Keeping cmp beans in synch


 Hi.

 This might be a silly question but i'll ask anyhow:

 How do i keep my entity beans in synch (so to speak)  if the data the
bean
 is mapped to is updated in the datasource by another application or
process
 ?

 what i'm experiencing is this: I use entity beans to cerate records in a
 dabatabse; my bean creates a record with pk_id = 1; then i remove the
record
 from the database and initialise my sequence class back to 1 so when i
call
 my bean.create i expect it to create a record with pk_id 1 again; but when
i
 do this i get all sorts of ejbexcpetions errors;

 this leads me to believe that i'm upsetting the caching of jboss; can
anyone
 point me in the right direction as far as what i am doing wrong;

 thanks.


 Chris Tragas
 -
 [EMAIL PROTECTED]

 -
 www.atomicmedia.com
 -



 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-user


___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



RE: [JBoss-user] Keeping cmp beans in synch

2001-06-28 Thread Chris Tragas

thanks guys; all under control now;


Chris Tragas
Information Services Manager
-
[EMAIL PROTECTED]
+61 3 9695 5711 direct
+61 3 0402 28 10 20 mobile
-
a t o m i c m e d i a
Leading Partners Online

Level 1 / 216 City Road
Southbank, Melbourne, Vic 3006
Australia.

+61 3 9695 5777 tel
+61 3 9695 5700 fax
-
www.atomicmedia.com
-



 -Original Message-
 From: Allen fogleson [mailto:[EMAIL PROTECTED]]
 Sent: Thursday, June 28, 2001 5:00 PM
 To: [EMAIL PROTECTED]
 Subject: Re: [JBoss-user] Keeping cmp beans in synch
 
 
 Do you remove it by calling the database or the remove() of 
 the entity bean?
 if the former... look at your default standardjboss.xml and change the
 commit option from the default of A. This presumes that the ejb has
 exclusive access to the database. you want either B (caching but non
 exclusive access) or C (non caching state loaded at the 
 beginning of each
 transaction)
 
 al
 
 - Original Message -
 From: Chris Tragas [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Thursday, June 28, 2001 1:06 AM
 Subject: [JBoss-user] Keeping cmp beans in synch
 
 
  Hi.
 
  This might be a silly question but i'll ask anyhow:
 
  How do i keep my entity beans in synch (so to speak)  if 
 the data the
 bean
  is mapped to is updated in the datasource by another application or
 process
  ?
 
  what i'm experiencing is this: I use entity beans to cerate 
 records in a
  dabatabse; my bean creates a record with pk_id = 1; then i 
 remove the
 record
  from the database and initialise my sequence class back to 
 1 so when i
 call
  my bean.create i expect it to create a record with pk_id 1 
 again; but when
 i
  do this i get all sorts of ejbexcpetions errors;
 
  this leads me to believe that i'm upsetting the caching of 
 jboss; can
 anyone
  point me in the right direction as far as what i am doing wrong;
 
  thanks.
 
 
  Chris Tragas
  -
  [EMAIL PROTECTED]
 
  -
  www.atomicmedia.com
  -
 
 
 
  ___
  JBoss-user mailing list
  [EMAIL PROTECTED]
  http://lists.sourceforge.net/lists/listinfo/jboss-user
 
 
 ___
 JBoss-user mailing list
 [EMAIL PROTECTED]
 http://lists.sourceforge.net/lists/listinfo/jboss-user
 

___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user



[JBoss-user] Keeping cmp beans in synch

2001-06-27 Thread Chris Tragas

Hi.

This might be a silly question but i'll ask anyhow:

How do i keep my entity beans in synch (so to speak)  if the data the bean
is mapped to is updated in the datasource by another application or process
?

what i'm experiencing is this: I use entity beans to cerate records in a
dabatabse; my bean creates a record with pk_id = 1; then i remove the record
from the database and initialise my sequence class back to 1 so when i call
my bean.create i expect it to create a record with pk_id 1 again; but when i
do this i get all sorts of ejbexcpetions errors;

this leads me to believe that i'm upsetting the caching of jboss; can anyone
point me in the right direction as far as what i am doing wrong;

thanks.


Chris Tragas
-
[EMAIL PROTECTED]

-
www.atomicmedia.com
-



___
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user