New answers tagged


What you have there seems like a standard architectural solution for MVC applications. Since MVC does not provide a solution for the data layer you have a repository. So the 3-tiers are: Business layer: where your classes appended by "Manager" are Data layer: repository Presentation layer: View and Controller EDIT: You should change the word "Manager" ...


This depends heavily on the filesystem and the operating system. For example, on Unix, there are no folders at all: Windows has completely different terminology. Classic MacOS had a different terminology, which, in OSX, is now mixing with Unix terminology.


It really depends upon the file system and the operating system. In POSIX and Unix, a file can be a directory, a plain file, a block device, a character device, a FIFO, a socket, a symbolic link, ... See POSIX stat & Linux stat(2), notice that file can have different types. So if you want to speak of a file whose type is plain and which is a sequence ...


As of now you have one ModelDevice class (Device in the model package). What if you have another such ModelDevice for a different classification? The problem may still persist and the overheads will also continue to increase. Though for the time being you may find that renaming classes be of some good help, for a long run the suggested alternate is to go ...


Use the package name. This type of problem is precisely why Java uses the package naming convention that it does. It prevents these sorts of problems, whether it's two teams in the same company or two teams on opposite sides of the earth.

Top 50 recent answers are included