I am having bad time debugging with this problem. I am migrating my codes from Java 1.4 to JDK 6 and Weblogic 8.1.5 to Weblogic 10.3. I have converted the deployment descriptors of EJBs using DDConver
I am learning EJB and I am trying to execute the Helloworld example given in EJB In Action book. My app server is JBoss, I created the Jar file for the bean class and interface in the right directory
I want to build a factory class which: instantiates a new instance of an EJB on a server returns the remote interface to that bean to the client
Environment: GlassFish 3.0.1, NetBeans 6.9, JDK 6u21 Also tested with GlassFish 3.0.1, NetBeans 6.9.1, JDK 6u22, but results are the same.
I\'m working with EJBs...I do the following and I don\'t know why the injected EntityManager is not working as one might expect.
I have a small Java2EE application, which is planning to grow in time (not very soon). Now I\'m trying to select the optimal fre开发者_Go百科e open-source production environment for it. I have two var
I have a simple EJB app that used to work about 6 months ago. I installed the latest JDeveloper (11.1.1.3.0) and I\'m trying to get it to work again, when I ran into this problem.
IN EJB-QL I am trying to create a query like this: SELECT * FROM table WHERE id IN ([id1],[id2],[id3],...);
When I have an @Asynchronous method in an EJB, and I don\'t specify the @TransactionAttribute, then how exactly does the container handle the transaction boundaries? Obviously, it can\'t use the call
As described in OpenEJB docs, we can configure JMS connection factory and queues, and they will appear in JNDI as: