Reputation: 342
Colleagues,
Could you please help me to resolve the following issue?
I have JAVA EE application. That contains a few Message Driven Bean with business logic and a few managerial beans that responsible for different aspects of configuration of entire application. I would like to setup the order of bean startup and initialization. It means the Message Driven Bean should not be called by container until managerial beans complete initialization of application. Initialization of application includes reading and parsing a few configuration files and it take us some period of time.
Upvotes: 0
Views: 371
Reputation: 2018
It'd depend on how things are packaged for this approach to work, but it's possible it could help. In the administrative console under "Applications" -> "WebSphere Enterprise Applications", select your app name, then select "Manage Modules". That should bring up a list of the EJB and web modules in your application. When you select one, the module's configuration page will include a "Starting Weight" value, which specifies when it starts - modules with lower weights will start first. It defaults to 5000 for all modules, but there's no real rules for magnitude, so simply pick some numbers and order them however you need.
Upvotes: 1