On 11/28/18 4:14 AM, Nikola Malenic wrote:
But how does the injection work with other stuff from modules, e.g.
The EntityManager injection  is also not handled for global modules,
since global modules do not get processed as deployments.
If you want to include JPA code in your global module, you could use the
javax.persistence.Persistence API  to create the EntityManagerFactory
from which you can get the EntityManager.
From: David Lloyd [mailto:email@example.com]
Sent: Tuesday, November 27, 2018 10:46 PM
Cc: WildFly Dev <wildfly-dev(a)lists.jboss.org>
Subject: Re: [wildfly-dev] Global module with ejbs
Correct, EJBs are not discovered from modules. They must be deployed.
On Tue, Nov 27, 2018 at 12:07 PM Nikola Malenic <nikola.malenic(a)netsetglobal.rs>
> I deployed a global module with remote ejbs defined, but I can't access them from
> Here is the interface:
> public interface ICryptoAPI..
> and bean definition:
> public class CryptoAPI implements ICryptoAPI ...
> How can I find jndi name of the ejbs deployed, since default @Ejb cannot find bean?
Just to mention, /subsystem=naming:jndi-view() from jboss-cli doesn't print anything
about deployed module and there are no errors in wildfly log.
> Maybe, it is not possible to define injectable ejbs in global modules?
> wildfly-dev mailing list
wildfly-dev mailing list