Hi,

Jay SenSharma

Jay SenSharma

WebLogic 10 onwards we can build and deploy EJB3.0 applications in WebLogic Server.

EJB3 features in WebLogic 10 onwards:
.
Point-1). java    weblogic.ejb.container.dd.xml.EjbAnnotationProcessor YourEjb.jar
you can use the above command to see the XML version (Means Deployment Descriptors) of your EJB3.0 annotation configurations.
.
Point-2). From WLS10 onwards The default transaction attribute is now “Required” In previous versions of WLS The default transactional attribute was “Supports
.
Point-3). JNDI name of EJB can be set using “mappedName” attribute of EJB annotations attribute.
.
Point-4). The default JNDI name format for your EJBs will be following:
<mappedName>#<qualified business interface name>

Example: In below case the JNDI name should be “MyBeanMappedName#aaa.bbb.MySLSBRemote”
package aaa.bbb;
@Stateless(mappedName=”MyBeanMappedName”)
@Remote(aaa.bbb.MySLSBRemote.class)
public class MySLSBBean implements MySLSBRemote
{
//some code
}
.
Point-5). If you want to make the JNDI name of your EJB simpler…means if you want to have a Custom JNDI name then you can use:
<business-interface-jndi-name-map> element in weblogic-ejb-jar.xml
.
Point-6). @EJB annotation can be used to inject both Local and Remote ejb-refrences.
.
Point-7). EJB 3.0 session beans can still declare a Home Interface for backward compatibility.

.

.

Thanks

Jay SenSharma

If you enjoyed this post, please consider leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.