Hi ranchers,
I'm just thinking about all things, that can cause automatic failure and are not described or let's say they are 'hidden' in assignment text.
Things than cause automatic failure are described explicitily in assigment:
As noted at the beginning of this document, where this document uses the word "must" an absolute requirement is being described. If you fail to adhere to such a requirement, your assignment will be failed automatically, and without further evaluation. It is therefore imperative that you pay close attention to any statement using the word "must" in this document.
I think there isn't hidden failures, they are explicity to says "any statement using the
word "must" in this document".
why do you want to do it when it's never used outside the package?
any classes which don't belong to the public api should not be declared public.
It depends where you want use your classes and interfaces, the two or three tier problem, for three tier it can works, but for two tier these classes can be used outside of the package (as i understand, i implement a three tier architecture). I didn't see a good reason to make it protected or default access in my project but classes hidden (databasemanager and lockmanager have default access modifier).
Regards.