Hi

Thanks a lot for all these answers.

> In non-managed environment - yes, with external transaction manager - no.

What are managed environments - how can I use them?

> use Statement.addBatch(String) and PreparedStatement.addBatch() methods.

I will look at this.

> Does not exist - feature is transparent, no additional steps are required.

Is it garanteed to be transparent? Aren't there any drawbacks?
What if the statement which originally prepared the statement is closed?
Will old PreparedStatements be discarded?
We have some classloading system, wich allows us to modify classes during
the runtime [which means new queries to be prepared]. The database-driver is
not reloaded. So we dont want the Cache to fill up.

> Depends on what's the state of auto-commit of the connection that created

that statement.

Thus the preparation is in no conjunction to the connection?

> Each connection has only one transaction. With one connection you cannot

execute two transaction simultanously.

Alright.

> Also you cannot log in using different users with one connection.

This is also impossible with the conncection pool, isn't it ?

> As long as you stay in auto-commit mode - yes.

Alright. (Will not do this - I assume this is bad design.)

> > All together, is there any "best practise for java connection pooling"

document?

> Not yet, it waits for somebody to write it.

If I get better in these things, maybe I will do it...
Right now, I don't feel experienced enough.


Regards,
Steffen