javadoc for SUN interface
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
Am I supposed to change the interface appropriately or should I refrain from doing so?
I got the impression that the interface should be not changed. But is this also true (just) for javadoc comments?
Any opinions are appreciated.
/Axel
Regards
SCJP, SCJD
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
<a href="http://www.newlatesttechnology.blogspot.com" target="_blank" rel="nofollow">more DownLoad here..</a>
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
my instructions tell me:
Your data access class must be called "Data.java", must be in a package called "suncertify.db", and must
implement the following interface
IMHO nowhere is said that the interface should stay unchanged. it's only required to not change its name and it should be in the db-package and the implementor-class should be called Data.java
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
However, I found another very interesting thread about it: Interface provided by Sun.
Cheers, Roberto Perillo
SCJP, SCWCD, SCJD, SCBCD
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
a) if they just do test (Data instanceof SunsInterface) then you can alter your interface as you want because that test will always be true if data implements SunsInterface (which is a must), so no automatic failure
b) doing a) + some checks via reflection: number of methods, names, parameters, exceptions thrown --> each modification will result in automatic failure
c) if they put your Data-class + your interface in an existing app with a class like Data2 (also implementing the required interface) every modification (new method, different method signature,...) of the provided interface will result in not compiling of Data2 and thus in automatic failure
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
What I understand from it, was:
Don't change the interface provided by SUN.
Put the javadoc comments in Data.java.
This is what I did, though my instructions clearly require to write javadoc style comments for each element of the public interface of each class. Which to be honest is vital with the central interface of the project, isn't it?
I do have
suncertify.db.DBAccess (SUN interface - no javadoc comments)
suncertify.db.Data (my implementation - with javadoc comments)
The generated javadoc looks weird to me as it only listens the signature of the methods in SUN's interface with no dpcumentation.
Is this what you suggested or did I miss anything?
Regards
SCJP, SCJD
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
/** {@inheritDoc} */
public int create(final String [] data) throws DuplicateKeyException { ... }
Cheers, Roberto Perillo
SCJP, SCWCD, SCJD, SCBCD
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
I'm trying to evaluate whether I can add javadoc comments to the interface provided by SUN as there are only implementation comments in it but my instructions clearly states to write javadoc style comments for each element of the public interface of each class.
This requires me to change it, right?, though as many members here propose not to touch the interface at all.
What should I do?
Regards
SCJP, SCJD
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
if you interprete that sentence very strict, then you don't have to add javadoc style comments to every interface you use, because you only must add it to "public interface of each class" and an interface is an interface, not a class
Kind regards
Roel
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
Axel Leucht wrote:I think you missed the point here.
Oh, sorry. Please try to be more clear next time.
Cheers, Roberto Perillo
SCJP, SCWCD, SCJD, SCBCD
-
-
Number of slices to send:Optional 'thank-you' note:
-
-
I asked Sun a question on this and i'll share the answers with you.
The question:
The instructions tell me: "Your data access class must be called "Data.java", must be in a package called "suncertify.db", and must implement the following interface" and then the interface.
Can you alter the given interface (change method signatures, add new methods, add javadoc to methods,...) or will this lead to automatic failure? Because nothing is said about this in the instructions. It's not a must to not change it, but (depending on the automatic failure tests used) altering the given interface could lead to automatic failure
Could you clarify on this please?
Their answer:
| Did you ever grow anything in the garden of your mind? - Fred Rogers. Tiny ad: The new gardening playing cards kickstarter is now live! https://www.kickstarter.com/projects/paulwheaton/garden-cards |








