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 "EJB Bad Practices: Use of AWT/Swing"
Weilin Zhong (talk | contribs) |
Weilin Zhong (talk | contribs) |
||
| Line 21: | Line 21: | ||
==References == | ==References == | ||
| − | [1] | + | [1] Enterprise JavaBeans 2.1 Specification. Sun Microsystems. http://java.sun.com/products/ejb/docs.html. |
[[Category:API Abuse]] | [[Category:API Abuse]] | ||
Revision as of 14:26, 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 program violates the Enterprise JavaBeans specification by using AWT/Swing.
Description
The Enterprise JavaBeans specification requires that every bean provider follow a set of programming guidelines designed to ensure that the bean will be portable and behave consistently in any EJB container [1].
In this case, the program violates the following EJB guideline:
"An enterprise bean must not use the AWT functionality to attempt to output information to a display, or to input information from a keyboard."
A requirement that the specification justifies in the following way:
"Most servers do not allow direct interaction between an application program and a keyboard/display attached to the server system."
References
[1] Enterprise JavaBeans 2.1 Specification. Sun Microsystems. http://java.sun.com/products/ejb/docs.html.
