I currently have the following project structure I would like to get rid of the ear and deploy myapp1 and myapp2 on their own. I tried to make myapp-ejb.jar a maven dependency of the two war and everything works fine at compile time. Nevertheless, there are a lot of jndi lookups in the code that fail at deploy time. Is
Tag: java-ee-6
@RequestScoped + new thread
We use javaEE RequestScoped with OpenLiberty and new threads via EJB @Asynchronous. I am just curious what the actual value comes from when we inject RequestScoped bean inside a new thread? Will the RequestScoped bean be freshly initialized? Or will it be pulled from the latest request? Answer In OpenLiberty, you’ll get a new request scope every time you make
Enable/disable loading of MDBs OR ignore deployment error if MDB cannot connect to the server
[environment: java ee 6, jms 1.1, wildfly 10, wmq 9] I have to set up 9 Message Driven Beans that listen to different topics on 3 different servers: 1 Topic in DEV 4 in PROD 4 in TEST (one for each in PROD) The problem is that the topics are restricted to their respective servers, meaning that if for instance