Hey Edward,

> And further, if the jBoss CMP mechanism is changed (and 
> there's no reason
> why it shouldn't be, it's implementation detail you shouldn't 
> be looking at)
> or you change the container - all your code is broken.

Don't follow. Which code is broken ? Can you post an example ?

Simon

> -----Original Message-----
> From: Bordet, Simone [mailto:[EMAIL PROTECTED]]
> Sent: 13 December 2000 15:28
> To: 'jBoss'
> Subject: RE: [jBoss-User] Entity Bean becoming Dirty..
> 
> 
> Hey,
> 
> Aravind, you have to use commit option B or C for your entity beans.
> 
> What suggested by Edward won't work if you're using CMP, because the
> container does not ask to a CMP bean if it's changed to 
> decide to reload it
> from the DB.
> 
> Commit option is set in jboss.xml
> 
> HTH,
> 
> Simon
> 
> > Hi Aravind
> > 
> > Are you using CMP ? If so then you shouldn't really be accessing the
> > database directly - it's "implementation detail" of how jBoss 
> > happens to
> > implement CMP. Also you have problems like you describe.
> > 
> > Consider using BMP if you want complete control over the db and the
> > persistence mechanisms used by your beans.
> > 
> > Edward
> > 
> > PS
> > 
> > Here's a pseudo-code kludge for CMP - very horrible and very 
> > inefficient but
> > the only way I know you could even begin to do it with CMP ;-)
> > 
> > mySessionBean::doBulkUpdate()
> > {
> >     do bulk update
> >     get home interface
> >     for each modified entity
> >             home.findbyPrimarykey();
> >             entity.markDirty();
> > }
> > 
> > -----Original Message-----
> > From: Aravind Ajad Y [mailto:[EMAIL PROTECTED]]
> > Sent: 13 December 2000 14:37
> > To: [EMAIL PROTECTED]
> > Subject: [jBoss-User] Entity Bean becoming Dirty..
> > Importance: High
> > 
> > 
> > Hi All,
> > 
> > I am having a situation where I am using an entity bean is 
> > used to represent
> > a row in the database.
> > I also have another situation where I have to update multiple 
> > rows in single
> > transaction.  Since it
> > bulk update, I am using a stateless session bean to call the 
> > update query.
> > Now since the database
> > is updated by Stateless Session Bean the data hold by the 
> > entity bean became
> > dirty.  How can I update
> > the data in the entity beans that are dirty.
> > 
> > regards,
> > Aravind.
> > 
> > 
> > 
> > 
> > --
> > --------------------------------------------------------------
> > To subscribe:        [EMAIL PROTECTED]
> > To unsubscribe:      [EMAIL PROTECTED]
> > Problems?:           [EMAIL PROTECTED]
> > 
> > 
> > --
> > --------------------------------------------------------------
> > To subscribe:        [EMAIL PROTECTED]
> > To unsubscribe:      [EMAIL PROTECTED]
> > Problems?:           [EMAIL PROTECTED]
> > 
> 
> 
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]
> 
> 
> --
> --------------------------------------------------------------
> To subscribe:        [EMAIL PROTECTED]
> To unsubscribe:      [EMAIL PROTECTED]
> Problems?:           [EMAIL PROTECTED]
> 


--
--------------------------------------------------------------
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Problems?:           [EMAIL PROTECTED]

Reply via email to