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".
