It looks like your app needs beanManager as in CDI.
but without full stacktrace it is really hard to help you.
I sometimes get the same message while redeploying an application from JB Dev Studio, normally goes away if I restart the server.
FWIW I'm experimenting with JAX-RS as SLSB, still don't use any CDI bean.
> It looks like your app needs beanManager as in CDI.
The app runs on Glassfish 4. What do I have to change to inject beanManager?
There is no stacktrace, the only other thing in the log is
2014-02-17 16:05:11,569 FINE [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-5) javax.naming.NameNotFoundException: BeanManager -- service jboss.naming.context.java.module.SQLJBatch.SQLJBatch.BeanManager
One concern is that the bean manager isn't available to the deployer until the INSTALL phase. Perhaps that is part of the issue. Or perhaps there is no bean manager being created for your deployment.
Can you post the server.log output from start of deployment, up to the error? Perhaps also enable TRACE logging for org.wildfly.extension.batch. Some instructions for enabling TRACE logging are here (for JPA but they should be helpful here also).
Do you have a beans.xml file? I realize this is no longer required, but I'm curious if adding one will solve the issue.
James R. Perkins
I had a beans.xml with length 0, but in WEB-INF/classes (which was fine for Glassfish).
Moving beans.xml to WEB-INF made the problem go away.
Thank you very much,