I've got two separate deployments that have Singleton EJBs that start up in parallel when the app server restarts. One of the EJBs attempts to look up the other EJB in its @PostConstruct method - only this tends not to work when they're deployed in parallel due to the other EJB not being available yet.
Given that they belong in separate deployments, is there any way to ensure that one EJB has started before another? (e.g. a JNDI @DependsOn).
Note: a delayed start up on the depending EJB would be just as good.
No input on this? To followup on the question, i'm specifically looking for a way to ensure the @PostConstruct of another EJB has been run before my calling EJB code is invoked.