Well I am not sure what the spec says, but in GemStone/J the transaction
context is propagated with the thread and along any distrubted component
invocations. So within a single JVM the transaction context propagates
through the thread. I would expect other servers to do similar?
-Chris.
> -----Original Message-----
> From: Frank Sauer [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, April 25, 2000 6:26 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Transaction context: Session Bean - non EJB - Session
> Bean
>
> I'm not sure. How would the transaction context get propagated
> through the non-bean object to the second session bean?
>
> Frank
>
> > -----Original Message-----
> > From: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Chris Raber
> > Sent: Tuesday, April 25, 2000 1:29 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Transaction context: Session Bean - non EJB -
> > Session Bean
> >
> >
> > Sounds like a bug. Check with WL forums...
> >
> > -Chris.
> >
> > > -----Original Message-----
> > > From: Graham Parsons [SMTP:[EMAIL PROTECTED]]
> > > Sent: Tuesday, April 25, 2000 8:21 AM
> > > To: [EMAIL PROTECTED]
> > > Subject: Transaction context: Session Bean - non EJB -
> > Session Bean
> > >
> > > We have a Session Bean that calls a non-EJB Java class
> > which in turn calls
> > > another Session Bean.
> > >
> > > If we make both beans container managed transaction
> > demarcation, and the
> > > business method on the second bean have a "MANDATORY" transaction
> > > requirement, we get a transaction does not exists error.
> > >
> > > However, I am told that if we make the first bean bean
> > managed transaction
> > > demarcation then all seems to work.
> > >
> > > The deployment environment is Weblogic 4.5.1.
> > >
> > > Any ideas ?
> > >
> > > Regards
> > >
> > > Graham
> > >
> > >
> > >
> > ==============================================================
> > ============
> > > =
> > > 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".
===========================================================================
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".
