> Ok, so if I understand this properly, for Spring transaction support > TransactionAwareDataSourceProxy must be used. Which means loss of > performance even for non-transaction changes. Or is there a way without > proxy?
I don't know Spring well enough to tell you whether this is the best way to do it. I usually configure pooled DataSources in a J2EE container. Why do you think there will be a loss of performance? If you wish to use shared data sources, then you will have to live with the overhead a container (or Spring) creates. If you can handle the JDBC connection yourself, you can also just create it using the JDBC DriverManager... In any case, for detailed questions about transaction management, you might have better luck asking your question on http://stackoverflow.com... Cheers Lukas
