|
| Java EE 5 Project Support: |
J2EE project wizards now support creation of Java EE 5 Web, EJB and enterprise (EAR) projects. Each of the respective project create wizards includes the Java EE 5 option.
Upon completion of the New Project Wizard the Java EE 5 libraries have been added to the project's build-path. These design-time libraries enable you to create Java EE 5 artifacts without experienceing compilation errors.
|
|
Attach src & Javadoc to MyEclipse J2EE Libraries
|
You can now attach source code and javadocs to the MyEclipse system libraries.
|
|
|
| EJB3 Projects: |
Since MyEclipse 5.5 supports JEE5, you can create a new EJB3 project by using the new EJB project wizard.
A new Java Enterprise specification level is available for EJB3 (Java EE 5.0).
If you wish, the wizard can generate a persistence.xml file for you automatically (optional).
|
|
| EJB3 Code Generation: |
You can now Reverse engineer EJB3 (JPA) Entities and Facades to your EJB3 project using the EJB3 Reverse engineering wizard.
Here is a sample of the generated code after reverse engineering.
From the toolbar, you can use the new EJB3 bean wizards to generate Entity, Session and Message Driven beans.
New EJB3 Entity Bean Wizard
New EJB3 Message Driven Bean Wizard
New EJB3 Session Bean Wizard
|
|
| Miscellaneous: |
For other features concerning Entitiy beans, please see the JPA section. |
|
| JPA Projects: |
In MyEclipse 5.5, you can now add JPA capabilities to any Java project.
MyEclipse allows you to select either Toplink or Hibernate as your JPA implementation.
Create a persistence unit easily using existing connection details.
Here is an example of a generated persistence.xml file.
|
|
| JPA Code Generation: |
From the DB Browser, reverse engineer JPA Entities and DAOs to your JPA project using the JPA Reverse engineering wizard.
Here is an example of some generated code from the JPA reverse engineering.
|
|
| JPA Validation: |
The JPA Entity Validator validates your entity annotations.
Referenced tables and columns are validated against your schema.
Annotation and mapping errors are also detected.
|
|
| Java Persistence Perspective: |
The MyEclipse Java Persistence perspective presents a convenient organization of views for working with JPA and EJB3 projects.
|
|
| JPA Details View: |
The Persistence properties view allows you to easily add new annotations and edit existing annotations without having to know JPA annotation specifics.
The table and column lists will be automatically populated with values from your schema.
|
|
| Database Metadata Settings: |
You may change the database and schema your project is associated with using your project's Persistence Properties page at any time.
If your schema has changed, the changes can be picked up by using the Rebuild JPA Metadata action. Your project will be automtaically validated against the updated schema.
Entities generated during reverse engineering are automatically added to the persistence.xml file. If you have unlisted entities in your project, use the Synchronize JPA Entity Classes action.
 |
|
| XFire 1.2.6: |
MyEclipse Web Services has been upgraded to the latest version of the XFire Web Service framework, version 1.2.6. XFire 1.2.6 incorporates several new features, enhancements and fixes over the 1.2.2 version shipped in the MyEclipse 5.1.1 release. See the XFire 1.2.6 release notes for a full listing of the changes. Existing Web Service projects will be automatically upgraded to use the new libraries. |
|
| WSDL Validation Enhancements: |
WSDL files used by the Top-Down Service Wizard and the New Web Service Client wizard are now validated before the code generation process. WSDL validity and WS-I compliance are checked, giving you the opportunity to correct any mistakes before generating code.
Profile compliance and validation settings for validation of WSDL files in the WSDL editor can be made at both workspace and project levels.
 |
|
| Spring 2 Support: |
MyEclipse 5.5 now supports Spring 2. Spring 2.0.5 is bundled with this release. We will continue enhance this feature set over the next few releases.
 |
|
| Spring 2: Adding Spring 2 Capabilities: |
New Spring projects are set to use Spring 2 by default.
Spring 2 projects use the new schema based config files.
The HQL Editor and Criteria Editor now work with Spring 2 projects. For more information, see the Hibernate section.
|