• Migration to MyEclipse
  
• Wizards
• Migrated Project
  

• WebSphere 6 Portal Server Support
• Add capabilities
• Deployment support
  
• Portal Project Wizard
• Portlet Wizard

• Enhanced Preview
  
• Custom Facelet Libraries
• Enhanced JSF Config Editor
  
• web.xml Editor
  

• Hibernate 3.2 and Annotation support
• Mapping Editor
• Query improvements

• Wizards
  
• Auto population
• Deployment
  

• Add Maven capabilities
  
• Add dependency
  
• Import Legacy Jars

• Java EE 5 JAX-WS
• Target Server Specification

• Spring 2.5
• Explorer
• AOP support
• Refactoring
• Validation Control
• Mylyn integration
• Web flow
  

On Finish, the wizard migrates the original project to a MyEclipse project. By default, the "_Migrated" is added to the original projects name for easy identification.

MyEclipse now allows you to create Web, WebService, and EJB projects with Maven cabilities, in addition to all the normal tooling you expect from these MyEclipse projects

MyEclipse 6.5 Blue Edition introduces support for the JAX-WS framework based on version 1.1 of the Metro stack. Metro is the JAX-WS reference implementation for Java EE 5.

JAX-WS web services and web service clients may be generated without having WebSphere 6.1 with the Feature Pack for Web Services installed.

Support for the WebSphere specific JAX-WS framework is also available as before.

For more details, see JAX-WS Framework support. 

Target servers used for WebSphere 6.0 and 6.1 generation are now profile specific, taking advantage of the new multi profile support introduced in 6.5.

MyEclipse 6.5 Spring Tools are based on Spring IDE 2.0.4 and include enhancements and optimizations specifically tailored for seamless operation with the MyEclipse application development technology stack.

MyEclipse 6.5 adds support for Spring 2.5. MyEclipse 6.5 bundles Spring 2.5.4.

Spring 2 libraries have also been upgraded to version 2.0.8.

The Spring Explorer view will also specially annotate any beans defined via Spring Java Configuration.

All Spring projects will contain a "Spring Elements" child when seen in the Project Explorer view. This item can be expanded to show beans, config sets and web flow definitions just like the Spring Explorer view described above. The ability to see list of all beans which reference a particular Java class is a key feature.

LIke the Spring Explorer, the Spring elements shown in this view can be filtered and customized. You can also use a special Spring working set to cut down the clutter in the Project Explorer.

The Beans Cross References view will show you all beans being advised as well as those which advise other beans.

The Spring Configuration editor as well as the Java editor will display special markers for methods and classes affected by your project's AOP configuration.

The Spring AOP Event Trace view will give you an idea of what is going on under the covers as Spring IDE's internal AOP model is being built.

AOP support requires the AOP Reference Model Builder which can be enabled / disabled at both the project and global level. If you do not use AOP in your projects, you can turn it off globally.

In addition to the Bean search, you can now search for Pointcut Matches in your workspace from the Search menu.

The new Spring Bean Definition wizard allows you to easily create configuration files with required namespaces.

The Spring Configuration editor is also namespace aware and will provide intelligent content assist and validation for defined elements.

Autocompletion in the popular 'p' namespace:

Renaming a Java class will now automatically make changes in bean definitions referencing that class. Java classes may also be renamed directly from the bean configuration file.

Bean Ids may also be renamed.

Renaming a bean property will make changes in corresponding Java class.

Validation settings can be controlled at a project (Project Properties > MyEclipse > Spring) or a global level (Window > Preferences > MyEclipse > Spring).

If you have Mylyn integrated, the Spring Explorer, Beans Cross References and Project Explorer view will allow you to filter the displayed content based on "level of interest". This includes bean definitions and referenced Java classes.

Content assist proposals will also be sorted based on their "level of interest".

MyEclipse 6.5 also adds Spring Web Flow support. 6.5 Milestone 1 includes Spring Web Flow 1.0.5 libraries.

Use the graphical editor to easily create states, actions and transitions.

Web flow definition files may also be edited in the XML editor with web flow specific content assist support.

Validation for web flow definition files is customizable.

All the configuration details needed for the instance are automatically read from the profile and auto populated in the fields. Users are also free to edit or provide additional information if desired.

On Finish, the wizard completes the instance creation process and updates the Servers view as shown below. All instances can be started/stopped from this view.

MyEclipse 6.5 includes Hibernate 3.2 and Hibernate Annotations support.

The reverse engineering wizard can generate annotated POJOs instead of simple POJOs and mapping files (hbm.xml).

Annotation support is also available for Spring - Hibernate projects.

HQL and Criteria editors continue to work when Hibernate annotations are used, even in Spring - Hibernate projects.

With the new Design page and accompanying wizards, editing mapping files is a cinch.

The HQL and Criteria editors now include a Max Results combo with which you can restrict the number of results returned by a query.

Content assist is provided for HQL queries in @NamedQuery annotations, these queries will also be validated.

Note: The HQL / Criteria editor for the project must be opened at least once per session for the above features to activate. This process will be improved in future releases.

While editing a NamedQuery annotation, you can invoke quick fix (usually Ctrl + 1) inside the query attribute to get a Copy to HQL Editor action.

Selecting this action will open the HQL editor, initialized with the query string. You can test and edit your query in the HQL editor, when done, closing the editor will allow you to copy the modified query back into the query attribute in the Java editor.

Similarly, when typing out a Criteria in the Java editor,  selecting it and invoking quick fix will show you a Copy to Criteria Edior action.

Selecting this action will open the Criteria editor, initialized with the selected text. You can test and edit the criteria in the Criteria editor, when done, closing the editor will allow you replace the originally selected text with the modified criteria query.