Enterprise JavaBeans (EJB) technology is the server-side component architecture for Java Platform, Enterprise Edition (Java EE).
EJB 3 specification defines the new simplified EJB API targeted at ease of development. It also includes the new Java Persistence framework, JPA
This EJB Interview questions test will help you prepare for interviews
You can also check out this post
Difference between Spring’s Transaction management and EJB’s Container managed transaction
There is no standard way as per Java EE specs for JNDI naming conventions, hence most of the application servers have their own way of JNDI naming.
On specifying a Datasource’s JNDI name as ‘myDatasource’, JBoss binds as ‘java:myDatasource’. So if one want to deploy the application on Jboss application servers then can use the simplest way is here. The steps for adding and using jndi Datasource to JBOSS 4.x is as under-
- Copy the jdbc driver to JBOSS_HOME/server/default/lib.
- Create the jndi xml file for datasource – example ds.xml Read more…
JMS Interview questions have been added to Skill-guru repository . Take the test to check your knowledge.
One of the gurus has added SCBCD mock tests on skill-guru which also has conceptual questions on EJB . These questions also cover EJB Interview Questions which are generally asked in interviews
I was a big fan of EJB’s CMT (Container managed transaction) feature because it reduces the developer of complex task of managing transaction through code. One of the biggest drawback of this was that this feature could only be used with EJB’s and not ordinary Java classes.
Then came the Spring’s Transaction management feature which changed the way applications can manage transactions. We will explore about Spring’s transactional capabilities and if they are better than EJB’s transaction