I’ve seen this come up here a few times, but in the postings I’ve seen, no one explained it. Why shouldn’t I extend JFrame (or any component)? Are there conditions where I should extend a component, or is this a firm rule that you don’t?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve seen this come up here a few times, but in the postings I’ve seen, no one explained it. Why shouldn’t I extend JFrame (or any component)? Are there conditions where I should extend a component, or is this a firm rule that you don’t?
Generally speaking, extending the component tends to be done strictly to use the component. This severely limits your options in unnecessary ways in terms of design, so that your classes can’t extend different classes, you can’t hide the JFrame’s methods causing it to be more difficult to maintain and easier to trigger unexpected bugs when using the class.
Typically the intention is strictly to use the class to draw a frame, and composition is preferred over inheritance.
That being said, subclassing should be fine when you intend your subclass to add project-specific functionality to the Frame (such as convenience methods and the like) where the subclass would be used instead of the Frame itself, but used as a frame in general, not as a view of a specific frame in the application.