Have you installed service pack 5 or 6?
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Kalam Sujeevan
Sent: Monday, November 20, 2000 6:02 PM
To: [EMAIL PROTECTED]
Subject: data read in a transaction
Hi Guys,
We are trying to read the data in a session bean which is updated by another
session bean in the same transaction.But we are not getting the updated data
when we read from the database. Any properties need to be set!?
I don't think this is related to data isolation, right!
The environment used is Weblogic/Oracle
TIA
Sujeevan kalam
"Christensen, Kurt" wrote:
> I'm a transaction newbie, so bear with me...
>
> If we have a layered architecture where we have stateless session beans in
a
> services layer, and entity beans in a domain layer (i.e., the Gemstone
> "FoodSmart" architecture at www.javasuccess.com), would it be unreasonable
> to say that all session beans could have a TX attribute of "TX_REQUIRED",
> and all entity beans could have a TX attribute of "TX_MANDATORY"? This
seems
> appealing to me because:
>
> a) This would essentially force all entity beans to be called through
> session beans (what we want, at least in this architecture)
> b) This would allow for Java clients with user-managed transactions, but
> otherwise would force creation of new transactional contexts for methods
> called on the stateless session beans (also what we want in this
> architecture... any individual method call on a stateless bean either
> succeeds or fails, and stateless bean methods can call other stateless
bean
> methods to provide services, without creating new transactional contexts).
>
> I realize that this isn't appropriate in all cases (i.e., if we have a
> session bean that don't require *any* transactional context), but in
> general, setting the TX attributes in this way makes sense to me.
>
> Any comments?
>
> KurtC
>
>
===========================================================================
> To unsubscribe, send email to [EMAIL PROTECTED] and include in the
body
> of the message "signoff EJB-INTEREST". For general help, send email to
> [EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
