commons-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dirk Verbeeck <>
Subject Re: [DBCP] Management of transactions.
Date Tue, 25 Jan 2005 20:31:50 GMT
When working in a non-managed environment you have 2 main options.
1) You set autoCommit=true. In this mode all changes are automatically 
2) autoCommit=false. You as programmer are responsible for committing 
the changes.

If you have a simple program (with simple input screens) on a well 
designed database then you can user option 1. But most of the time you 
want to manage the database transactions yourself using option2.

Most (web) frameworks have a more or less standard practice where to 
put the commit statements. Using a business and DAO layer and hide you 
database access is better of course.

You can also work in a managed environment. The application 
server/container manages the transactions for you. An EJB server is 
the most known example but there are others like spring framework.

Hope this helps

ksv wrote:
> Hello ,
> Interests everything, that is connected to managements of transactions at use DBCP...
> Who Can will share experience or links? The database is not essential.
> The principle of work with transactions through DBCP is necessary...
> Best regards,
>  ksv                

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message