Hi,
We are obtaining JDBC connection using JNDI lookup. Instead of performing
JNDI lookup in each and every DAO we have written a Java class which
retrieves Connection object.
Regards,
Milind
Johan Eltes
<johan.eltes@ca To: Milind Kulkarni
<[EMAIL PROTECTED]>
llista.se> cc:
Subject: Re: Transaction Propogation
Non EJB class
01/24/2003
11:25 PM
How does your dao obtain the jdbc connection?
/Johan
Den 2003-01-24 12.27, skrev "Milind Kulkarni"
<[EMAIL PROTECTED]>:
> Hi All,
>
> In our architecture we are not using Entity Beans. From Session Bean we
are
> calling the respective Data Access Object (DAO). We are using a
> transactional data source. A declarative transaction is started in the
> session bean ( we are using 'Required' transaction attribute ).
>
> My problem is that we have 2 SQL statements in our DAO. After first SQL
> statement an exception takes place. Though second SQL statement is not
> executed but first SQL statement is committed - which is a problem for
us.
> Exception is propogted back to session bean and we are also using
> setRollbackOnly() method to tell container to roll back the entire
> transaction but it does not help. We are using WLS 6.1.
>
> Any tips / pointer will be appreciated.
>
> Regards,
> Milind
>
> *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> an attempt may be failure,
> but there should not be failure in an attempt
>
> - Albert Einstein
>
> -*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-
>
>
===========================================================================
> 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".