Developing Java EE applications using myeclipse: A preliminary discussion on EJB project development (i)

You start school, I put the price! MyEclipse Online Carnival continues! >> in hot Open

"MyEclipse Latest version download"

First, MyEclipse EJB development tools

Enterprise Java Beans (EJB) has the Jee/java EE 5 standard for implementing JAVA enterprise business functions and database resource interfaces. The MyEclipse EJB3 tool supports Java EE 5 's Pojo programming model based on simplified annotations. These tools enable you to develop and deploy a EJB3 bean in a few minutes. MyEclipse also supports traditional EJB2 development, using integrated xdoclet annotation processing to quickly develop JEE 1.4 Enterprise Java beans.

MyEclipse EJB development tools include:

• EJB Creation Wizard
• XML source and form-based editor for deployment descriptor customization
• EJB Deployment Services

In addition, MyEclipse provides a property-oriented programming environment for EJB Xdoclet.

• Java Editor enhancements to support code completion for Xdoclet annotations and Jee APIs
• Automatically generate EJB, home interface, and find tools
• ejb-jar.xml and Application Server-specific deployment descriptor generation

ii. EJB Project

The EJB project is basically a Java project that contains the folder structure of a decomposed EJB jar file. The main difference between an EJB project and a typical Java project is that the EJB project folder is decorated with a bean icon, and the project contains the runtime library, along with an opportunity to include a Ejb-jar.xml deployment descriptor file. Using all EJB projects that are below the Java EE 5.0 version creates the Meta-inf root folder and an empty meta-inf/ejb-jar.xml deployment Descriptor. This file is not required for projects that use JEE5 or later, and you can choose to generate this file for this purpose. You can modify the ejb-jar.xml file as needed.

myeclipse Preview view of EJB project

Also describes the project's metadata files, note that these files are usually hidden in the default Eclipse view by default. * File name filter, hidden point prefix. . Project and . Classpath culture are standard Eclipse project information files. Do not delete or modify these files. Similarly, if your project is made up of a source control tool such as CVS, be sure to include all of these files as part of your project.

Displays the deployment information for the MyEclipse EJB project, and if you do not create a build deployment descriptor in your project, you can right-click Deployment Descriptor placeholder and select Generate Deployment Descriptor stub.

Deployment Descriptor Information

Project deployment can use the deployment assembly property of the project.

Enterprise Archive (EAR) is the only deployment pattern specified by the JEE specification. However, the specification provides for application server-specific deployment models. Application servers such as JBoss and WebLogic support the direct deployment of EJB jar archives. The limitation of direct EJB jar deployment is that there is no provision for optional packages required to deploy an EJB jar archive.

You can set Java project Dependencies for EJB projects.

For more information, please visit MyEclipse Chinese network >>

Developing Java EE applications using myeclipse: A preliminary discussion on EJB project development (i)