Starting MDB on deployment

[phisatmonster]

Is there a way to configure a Message Driven Bean such that on deployment of the MDB to the app server, the MDB will be created and placed in the instance pool? I've seen in the configuration files that the container pool is configured to have a minimum size set with the element to 1, which would seem to say that on deployment 1 MDB of that type will get created and placed in the instance pool. However, on standard deployment, the bean does not get created until a JMS mesage is sent to the destination the MDB is associated with. I've been able to do this in the past with BEA WebLogic, but I am migrating to JBoss now. If anyone could confirm this is not possible, or explain a way to set up the MDB so that it is created on deployment, that would be much appreciated. Thanks!

[genman]

I don't think there is a way.

What do you need to do in the MDB when there are no messages to process?

[phisatmonster]

actually it's not so much that an MDB is needed, but any EJB. My problem is that I need to run a timer on the bean, and have the timer start on deployment, not the first access of the bean.