First, the verifier should check that you specify either a primary
key class or primary key field for entity beans.
Second, I don't think the "listener" approach to JMX MBean
ordering will work. Consider that the auto-deployer must deploy after
*all* databases have started. If it just listens for the database pool
bean (assuming it can listen on a class rather than instance, so it won't
have to know *which* pools are there), it may load after one of 10
databases, which would still cause problems. If we load all the instances
for a class at once (all pools, etc.) and it waits for that to complete,
it will never start if there are no pools. There may - may - be some way
around this if we let each MBean look at the entire list of MBeans before
it decides which ones to listen for, but this is getting pretty nasty...
I think it would be simpler for each MBean to list all the MBean
classes it depends on, and then load all the instances of those (where
available) first.
Aaron
