Yes, please do. In the JBAS project. Actually, I see two issues in this thread: 1) Figuring out why the @Depends on your EJB results in a different error message than the expected one that I got when I deployed my example POJO. 2) Coming up with a mechanism to avoid the ERROR message altogether when the missing dependency is due to a known, acceptable condition. Perhaps some SPI, where processors can register themselves with the service that logs this and be given access to the objects that drive the logging. An impl of the SPI that works with/is part of a BarrierController would flag relevant missing dependencies as not being error conditions. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4241545#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...