This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org
Difference between revisions of "J2EE Bad Practices: getConnection()"
Weilin Zhong (talk | contribs) |
Weilin Zhong (talk | contribs) (Removed Communication category.) |
||
| Line 38: | Line 38: | ||
[[Category:Java]] | [[Category:Java]] | ||
| − | |||
| − | |||
[[Category:Code Snippet]] | [[Category:Code Snippet]] | ||
Revision as of 14:37, 18 July 2006
- This article includes content generously donated to OWASP by
This is a Vulnerability. To view all vulnerabilities, please see the Vulnerability Category page.
Abstract
The J2EE standard forbids the direct management of connections.
Description
The J2EE standard requires that applications use the container's resource management facilities to obtain connections to resources.
Examples
For example, a J2EE application should obtain a database connection as follows:
ctx = new InitialContext(); datasource = (DataSource)ctx.lookup(DB_DATASRC_REF); conn = datasource.getConnection();
and should avoid obtaining a connection in this way:
conn = DriverManager.getConnection(CONNECT_STRING);
Every major web application container provides pooled database connection management as part of its resource management framework. Duplicating this functionality in an application is difficult and error prone, which is part of the reason it is forbidden under the J2EE standard.
