VariantDraft

CWE-575EJB Bad Practices: Use of AWT Swing

Category: other

Description

The product violates the Enterprise JavaBeans (EJB) specification by using AWT/Swing. 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. In this case, the product 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." The specification justifies this requirement in the following way: "Most servers do not allow direct interaction between an application program and a keyboard/display attached to the server system."

Common consequences· 1

  • Other — Quality Degradation

Potential mitigations· 1

  • [Architecture and Design]Do not use AWT/Swing when writing EJBs.

References

  1. https://cwe.mitre.org/data/definitions/575.html

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.

CWE
EJB Bad Practices: Use of Sockets
CWE
EJB Bad Practices: Use of Class Loader
CWE
EJB Bad Practices: Use of Java I/O
CWE
EJB Bad Practices: Use of Synchronization Primitives
CWE
J2EE Bad Practices: Non-serializable Object Stored in Session
CWE
Runtime Resource Management Control Element in a Component Built to Run on Application Servers
Sourced from MITRE CWE 4.20. Curated for EU compliance use cases by Adam Lundqvist, Founder at SQUR.