MyEclipse for Spring 9.0

Release Notes

What’s New in ME4S 9.0?

ME4S 9.0 Reference and Tutorials

JSF 2.0 Scaffolding

GWT 2.2 Scaffolding

Upgrading DSL Projects

ME4S 9.0 for ME Pro Users

JUnit Execution Classpath

What’s New in ME4S 9.0?

Please check out this blog post for a list of enhancements and new features for ME4S 9.0: ME4S 9.0: Smarter Auto Code Generation and Application Development for the Spring Framework

ME4S 9.0 Reference and Tutorials

The MyEclipse for Spring 9.0 reference guide and tutorials have been updated, and they are all available in ME4S help system.  Within the next few days they will all be available online here.  For now you can access them from the following links:

JSF 2.0 Scaffolding

Before scaffolding for JSF 2.0, you need to add JSF 2.0 capabilities to the project.  This can be done from the MyEclipse > Add JSF Capabilities menu option.

In order to run JSF 2.0 applications on MyEclipse Tomcat (or Apache Tomcat 6.0), you will need to update the expression language (EL) libraries in Tomcat.  The easiest way to update the EL libs is to prepend the new libraries in the classpath.

The EL libraries can be downloaded here: EL API and EL implementation

See tutorial for a detailed example of JSF scaffolding.

GWT 2.2 Scaffolding

Scaffolding GWT 2.2:

Upgrading DSL Projects

  1. For projects with Classpath Containers that use the DSL: Your project will get the new Spring 3.0.4 configuration added to your web-context.xml file so you should upgrade your Spring version, along with the other libs we've incremented like Hibernate.  We've re-organized some of our containers so the easiest thing to do is just remove all existing classpath containers from the build path with the exception of the JRE System Library, Java EE Libraries and the GWT SDK, then use the Add Runtime Dependencies wizard to add the new ones.  You can be intelligent on that wizard and leave off ones you're not interested in, like Google, Primefaces, etc.  The complete list of classpath containers provided by MyEclipse for Spring 8.6 that are safe to remove are:
  1. Apache Commons BeanUtils 1.8 Libraries
  2. Apache Commons DBCP 1.3 Libraries
  3. Atomikos 3.6.4 Libraries
  4. CXF 2.1.9 Libraries
  5. CXF 2.1.9 Support Libraries
  6. DWR 2.0.5 Libraries
  7. Derby 10.1.1.0 Client Libraries
  8. GWT 2 Libraries
  9. Hibernate Core Libraries
  10. JavaServer Pages Standard Tag Library (JSTL) 1.2
  11. Logging 1.5.10 Libraries
  12. Postgres JCBC 8.3 Libraries
  13. SiteMesh 2.4 Libraries
  14. Skyway Spring Utilities 7.1.1 Libraries
  15. Spring Core 3 Libraries
  16. Spring Flex & BlazeDS Libraries
  17. Spring MVC3 Libraries
  18. Spring Security 3.0.0 Libraries
  19. Spring Webflow 2 Libraries
  1. After you've upgraded the hibernate classpath container, you'll need to open the hibernate.properties file and remove the entry for the hibernate cache.
  2. We’ve eliminated the -generated- versions of configuration files but we don’t delete them from your project.  If you’ve enabled the DSL on your project, the content that was previously generated into your -generated- files is now merged into the non generated version.  With the exception of the -generated-flex-config file, the existence of the extra files cause no problems.  However, to increase maintainability of your project, it is recommended that you clean up the project by removing the extra files and all references to them.   To clean up the generated files, follow these steps:
  1. Back up your project by exporting it or adding it to a version control system.
  2. Remove all -generated- files (projectname-generated-web-context.xml, etc)
  3. Remove the references to the -generated- files from applicationContext.xml.  
  4. Remove the reference to the -generated-web-context.xml file from web.xml
  5. If you’ve scaffolded flex, remove the projectname-generated-flex-config.xml and remove the reference in web.xml.
  6. If you’ve scaffolded webflow, remove the projectname-generated-webflow-config.xml and remove the reference in web.xml.

ME4S 9.0 for ME Pro Users

If you are an ME Pro user and you would like to install/evauluate ME4S 9.0, we recommend that you use the MyEclipse for Spring add-on option.

Help → MyEclipse Configuration Center → Dashboard tab → MyEclipse Features → MyEclipse for Spring

JUnit Execution Classpath

In order to run the generated JUnit test classes, you will need to add JPA 2.0 libraries to JUnit execution classpath.  Here are the general steps:

  1. First you have to select the test class, right click and select Run As -> Junit Test.  This is so it will create a launch configuration.
  2. Next, select the test class, right click and select Run As -> Run Configurations….  Your launch configuration should be selected.
  3. Click on the Classpath tab.
  4. Click on the Bootstrap Entries item.
  5. Click on the Add External Jars.. button.
  6. Select the jar file that contains the jpa 2 classes,
  7. Select the jpa 2 jar file item under the Bootstrap Entries item and click the Up button so that it appears before the Java EE 5 Libraries item.