First and foremost: What I tried first was using the @PostConstruct annotation on a method that should be called after deployment – but that doesn’t work, because the EJB is not guaranteed to be instantiated directly after deployment. As a matter of fact, at least the JBoss I was using lazily instantiates the EJB the moment it is first invoked.

After a while, I came across this thread in Sun’s forum, in which a Sun developer states that better support for this use case is planned for a future EJB version, and currently the only way to achieve the desired effect is to rely on a ServletContextListener, which provides a contextInitialized() method that is called as soon as a servlet context is initialized. However, like the “servlet” implies, there needs to be a web application to use this listener – so I ended up adding a web application to my enterprise application with no content besides that context listener that would poke the EJB in order to get started. Now although this method is far from elegant, at least it works reliably and most possibly independent of the container used; at least I can verify its functionality on the JBoss 5 used in my test system.

Share/Save

• Aspect Oriented Programming (AOP)
• Object Manager featuring dependency injection
• MVC framework
• Persistence framework

…and many more.

The framework seems to be very interesting and sophisticated, and although I couldn’t yet find time to try it, I will definetly do so in the next time. The framework is developed in conncetion with the TYPO3 content management system and can thus be expected to be of high quality.

Share/Save