In this objective, it ws mentioned that exam takers should know how to describe and apply the "program to an interface" principle. Can anyone shed light to this principle?
Be Afraid...Be very Afraid...
Dave Wood
bronco
Ranch Hand
Joined: Aug 02, 2004
Posts: 161
posted
0
If you have a copy of Design Patterns handy (and if you don't, you SHOULD!), read pages 17-18 for a discussion of this topic.
In a nutshell:
Don't declare variables to be instances of particular concrete classes. Instead, commit only to an interface defined by an abstract class (Dave comment: or interface).
Note that this concept is not literally talking about Java interfaces (in the DP book, which is generally C++ oriented, they just talk about abstract classes), though they certainly apply.
There are not a lot of exam questions on this topic. You just need to understand the basic idea. For example:
HashMap hm = new HashMap(); // not programming to an interface
vs.
Map map = someFactory.createMap(); // programming to an interface
HTH, Dave
Co-Author of <a href="http://www.oreilly.com/catalog/jswing2" target="_blank" rel="nofollow">Java Swing</a><br />Co-Creator of <a href="http://www.sun.com/training/catalog/courses/CX-310-055.xml" target="_blank" rel="nofollow">SCJP 5.0</a> and <a href="http://www.sun.com/training/certification/java/associate_beta.xml" target="_blank" rel="nofollow">SCJA</a> exams
Mahesh Kumaraguru
Ranch Hand
Joined: Jun 01, 2005
Posts: 95
posted
0
Originally posted by Paulo Aquino: In this objective, it ws mentioned that exam takers should know how to describe and apply the "program to an interface" principle. Can anyone shed light to this principle?
"Program to an interface" is discussed with examples at
0
