My instructions do not require create or delete in the GUI, so I assume I don't need to implement the create and delete methods of the given interface.
But if this is true, what should I do in the class that implement the interface? Just return null?
I'm worried about "must implement this interface" means that I must implement all methods...
Did anyone loose points with this?
If you implements any class you have to provide implementation of all the method. If you think that this method is not full filling your need then donot write any think in body or donot implements the interface
You could take a risk and implement the given interface and for each method you don't use in the application throw an UnsupportedOperationException. Then extensively document in choices.txt why you followed this approach and you might pass with this approach. But it still is a risk you could possibly fail for not having an actual implementation for all methods. As far as I know no one so far took this risk, because it could be a costly one.
I agree with Roel. It is indeed risky to have an empty implementation.
For me too, requirements were similar (no necessity for create and delete operations, but given interface was containing those methods).
So, I wrote a descent working code for those methods, but did not expose those methods via RMI or did not provide any buttons on GUI. So, only way to invoke those methods was to write another class and call the methods.
Of course, I mentioned all these things in choices.txt.