I have been doing Java SE for some years now and moving on to Java EE. However, I have some trouble understanding some aspects of Java EE.
I have this code in an ejb for (PayrollEntry pe : payroll.getEntries()) { recalculateP开发者_运维技巧ayrollEntry(pe);
I know Stateless EJBs are stored in a pool and instantiated as needed, my question is, what happens when there are more EJB dependencies, for example with something like this:
My EJB project, packaged in an EAR, defines some env-entry configuration values in its ejb-jar.xml. I can inject these into my session bean fine.
I have am deploying 2 EARs onto JBoss AS 7.1.0.Alpha1-SNAPSHOT (post 7.0.1.Final version). Both deploy fine.
For example, can I do the following @Stateless @LocalBean public class MyBean extends AbstractFacade<MyBeanEntity>
In our J2EE application, we use a EJB-3 stateful bean to allow the front code to create, modify and save persistent entities (managed through JPA-2).
I am trying to inject an EJB with the @EJB annotation : when I inject an EJB into another EJB it works fine.
I have a weird (?) problem with an EJB I want to deploy to my Glassfish 3.1 application server. I have this bean, which should be executed continuously in Glassfish using the @Schedule annotation. T
I know that with the instruction: Persistence.createEntityManagerFactory(\"persistence-unit-name\"); The JPA persistence mechanism reads the \"persistence.xml\" file, looks for the persistence unit
加载中,请稍侯......