[jdjlist] Re: interface for only 1 class

[Greg Nudelman]

Title: interface for only 1 class

William,

 

This is a very important question.  I would read up on this. Here is an excellent resource, a truly remarkable article, that (IMHO) everyone should read at least once:

 

http://www.javaworld.com/javaworld/jw-12-1998/jw-12-techniques.html

 

Greg

-----Original Message-----
From: William Rice [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 03, 2002 8:50 PM
To: JDJList
Subject: [jdjlist] Re: interface for only 1 class

Sorry to but in, but I see you guys are talking about interfaces in JAVA.  I have been working with JAVA for about three months and I have come upon code that uses the JAVA interface,

 

I have worked in visual coding suce as visual foxpro and visual basic and when I here the word interface I think about a GUI.

 

What is the significance of the INTERFACE.

-----Original Message-----
From: James Stauffer [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 03, 2002 2:05 PM
To: JDJList
Subject: [jdjlist] Re: interface for only 1 class

How do you balance that will all of the times that an interface isn't necessary?  Another aspect is that an interface usually makes it more complex.  If there is no foreseeable need for an interface when should you use an interface and when shouldn't you?

 

James Stauffer

-----Original Message-----
From: Greg Nudelman [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 03, 2002 12:28 PM
To: JDJList
Subject: [jdjlist] Re: interface for only 1 class

It depends.  Let's say you only expect to use Oracle DB in the foreseeble future.  So you write your driver loading, and persistance all over the place, and create it only for the Oracle.  But in 12 months, your business folks decide to try and sell the system to some customer, who just got to have SQL Server.  If you wrote persistence as an interface, it is a snap, otherwise, some work and re-testing af the whole thing may be involved.

 

Sounds funny, but this is a real-life example.

 

Greg

-----Original Message-----
From: James Stauffer [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, December 03, 2002 7:54 AM
To: JDJList
Subject: [jdjlist] interface for only 1 class

Is it good to have an interface if there will only be one class to implement it in the foreseeable future? Does it add unnecessary complexity? It usually isn't much more complex but does that extra complexity add extra value? Agile programming seems to say "don't build it because you won't need it." What do you think?

James Stauffer

____________________________________________________
To change your JDJList options, please visit:
http://www.sys-con.com/java/list.cfm

Be respectful! Clean up your posts before replying
____________________________________________________

____________________________________________________
To change your JDJList options, please visit:
http://www.sys-con.com/java/list.cfm

Be respectful! Clean up your posts before replying
____________________________________________________ ____________________________________________________
To change your JDJList options, please visit:
http://www.sys-con.com/java/list.cfm

Be respectful! Clean up your posts before replying
____________________________________________________

____________________________________________________
To change your JDJList options, please visit:
http://www.sys-con.com/java/list.cfm

Be respectful! Clean up your posts before replying
____________________________________________________

____________________________________________________
To change your JDJList options, please visit:
http://www.sys-con.com/java/list.cfm

Be respectful! Clean up your posts before replying
____________________________________________________