it is a good practice to have a constants interface, but its a really
bad practice to perform hidden data accesses for constant
initialization. In your case a UtilityClass (static methods) with a
controlled initialization would be much better.
if ObjectDAO.get("APPLICATION") fails the results are pretty
undefined, since the whole interface will probably be unloadable by
the classloader and you'll get a lot of classnotfound exceptions...
leon
On 7/18/06, temp temp <[EMAIL PROTECTED]> wrote:
I have is a constants interface with static final fields .
Each field value is a call to DAO.
For example
interface IObjectTypeIds{
public static final int APPLICATION =ObjectDAO.get("APPLICATION");
}
Is this is a good practice ?
---------------------------------
Do you Yahoo!?
Everyone is raving about the all-new Yahoo! Mail Beta.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
