One (of many) problems with this approach is that it may fail to
initialize, but that won't happen until the class is loaded at first
use. If an application is broken because the database is inaccessible,
it's better to know at deployment. I use a servlet startup listener
(javax.servlet.ServletCo
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
absolutely not
-Original Message-
From: temp temp [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 18, 2006 3:43 PM
To: user@struts.apache.org
Subject: interface for constants
I have is a constants interface with static final fields .
Each field value is a call to DAO.
For example
interfa
3 matches
Mail list logo
