Jerome,
As DomainUpgrade is only a marker interface, and you *inject* the impl classes,
how can any errors be reported back to the users, if postConstruct encounters any?
For the EJB Timer Service, to upgrade the timer table, the underlining database
must be up and running. While this is not a problem in default case (when
embedded derby is used), if the setup was changed to use some other database, it
might have been stopped, and it would be nice to tell the user that they need to
execute themselves the alter statement from the fix xyz.sql.
thanks,
-marina