MyEclipse for Spring Reference – Blueprints
1. Web Layer – Spring MVC
Note: Spring scaffolding requires a MyEclipse Spring or Bling subscription.
The image below shows the Spring MVC scaffolding blueprint, and the following table describes what gets generated.
| Item | Description | ||
| Flows (Spring Web Flow) | one flow per domain object; each flow handles all users events for the managing domain object and related domain objects; including list, view, delete and add WebRoot/WEB-INF/flows/managedomain/managedomain.xml | ||
| Fully implemented request handlers | integrated with Service and DAO layers using Spring dependency injection See generated methods in Controllers | ||
| JUnit tests | one test method per request handler generated/<packageName>/DomainControllerTest.java | ||
| JSP pages | using JSTL, Spring form/javascript tag library; one set of pages per domain object Edit page – for editing and creating new records; localized; client-side validation List page – for listing all top-level records; localized View page – for read-only view of a record and listing related children records; localized Delete page – for confirming deletion of record | ||
| Application-level UI components | one set per application Header Footer Dashboard | ||
| Sitemesh configuration | for layout management
| ||
| Look and Feel |
| ||
| Spring context files for web layer |
| ||
| Internationalization Support | Localization bundles
| ||
| Web Flow Diagrams | for maintaining a web flow using graphical interface; each generated flow will have a matching diagram webFlowDiagrams/managedomain.webflow_diagram | ||
| Other generated applications layers to support Spring Web Flow application |
2. Web Layer – Spring WebFlow
The image below shows the Spring Webflow scaffolding blueprint, and the following table describes what gets generated.
| Item | Description | ||
| Flows (Spring Web Flow) | one flow per domain object; each flow handles all users events for the managing domain object and related domain objects; including list, view, delete and add WebRoot/WEB-INF/flows/managedomain/managedomain.xml | ||
| Fully implemented request handlers | integrated with Service and DAO layers using Spring dependency injection See generated methods in Controllers | ||
| JUnit tests | one test method per request handler generated/<packageName>/DomainControllerTest.java | ||
| JSP pages | using JSTL, Spring form/javascript tag library; one set of pages per domain object Edit page – for editing and creating new records; localized; client-side validation List page – for listing all top-level records; localized View page – for read-only view of a record and listing related children records; localized Delete page – for confirming deletion of record | ||
| Application-level UI components | one set per application Header Footer Dashboard | ||
| Sitemesh configuration | for layout management
| ||
| Look and Feel |
| ||
| Spring context files for web layer |
| ||
| Internationalization Support | Localization bundles
| ||
| Web Flow Diagrams | for maintaining a web flow using graphical interface; each generated flow will have a matching diagram webFlowDiagrams/managedomain.webflow_diagram | ||
| Other generated applications layers to support Spring Web Flow application |
3. Web Layer – JavaServer Faces 2.0
The image below shows the JavaServer Faces 2.0 scaffolding blueprint, and the following table describes what gets generated.
Item | Description | ||
| Managed Bean | one managed bean per domain object; each bean handles all users events for the managing domain object and related domain objects; including list, view, delete, and add
| ||
| Fully implemented request handlers | integrated with Service and DAO layers using Spring dependency injection See generated methods in JSF managed beans | ||
| XHTML pages | using JSF and Primefaces; one set of pages per domain object Edit page – for editing and creating new records; localized; client-side validation List page – for listing all top-level records; localized View page – for read-only view of a record and listing related children records; localized Delete page – for confirming deletion of record | ||
| Application-level UI components | one set per application Header Footer Dashboard | ||
| Sitemesh configuration | for layout management
| ||
| Look and Feel |
| ||
| Spring context files for web layer | WebRoot/WEB-INF/faces-config.xml | ||
| Internationalization Support | Localization bundles
| ||
| Other generated applications layers to support Spring Web Flow application |
4. Web Layer – Adobe Flex
The image below shows the Adobe Flex scaffolding blueprint, and the following table describes what gets generated.
Item | Description | ||
| Declarative UI components for Adobe Flex | Listing and Detail – for read-only view of a record and listing related children records flex_src/project/mxml/ManageDomain.mxml Edit Form – for editing and creating new records; client-side validation | ||
| Event handler in Actionscript | flex_src/<packagename>/DomainEvent.as | ||
| Domain model in Actionscript | flex_src/<packagename>/Domain.as | ||
| Look and Feel |
| ||
| Spring context files for Flex integration | WebRoot/WEB-INF/config/projectname-flex-context.xml | ||
| Flex configuration files |
| ||
| Flex compilation ant script |
| ||
| Other generated applications layers to support Adobe Flex application |
5. Web Layer – Google Web Toolkit (GWT)
The image below shows the Google Web Toolkit scaffolding blueprint.
6. Web Layer – iPhone
The the following table describes what gets generated.
Item | Description | ||
| Stateless annotation-based multi-action Spring Controllers (@Controller) | one controller per top-level domain object; each controller handles all users events for the managing domain object and related domain objects; including list, view, delete and add. generated/<packageName>/DomainController.java | ||
| Fully implemented request handlers | integrated with service and DAO layers using Spring dependency injection See generated methods in Controllers | ||
| JUnit tests | one test method per request handler generated/<packageName>/DomainControllerTest.java | ||
| JSP pages | using JSTL, Spring form/JavaScript tag library; one set of pages per domain object Edit page – for editing and creating new records; localized; client-side validation View page – for read-only view of a record and listing related children records; localized List page – for listing all top-level records; localized | ||
| Application-level UI components | one set per application Footer Dashboard | ||
| Sitemesh configuration | for layout management
| ||
| Look and Feel |
| ||
Spring context files for web layer | resources/projectname-web-context.xml | ||
| Internationalization Support | Localization bundles
| ||
| Other generated applications layers to support iPhone Web application |
7. Service Layer
The service layer blueprint applies to the Spring MVC, Spring WebFlow, JavaServer Faces (JSF 2.0), Adobe Flex, Google Web Toolkit (GWT), and iPhone web layer blueprints.
Item | Description | ||
| Service Interface | generated/<packageName>/DomainService.java | ||
| Stateless Spring Service w/ transaction management (@Service) | generated/<packageName>/DomainServiceImpl.java | ||
| Fully implemented service methods | integrated with DAO layer using Spring dependency injection | ||
| JUnit tests | one test per service methodgenerated/<packageName>/DomainServiceTest.java | ||
| Spring context file for service layer | resources/projectname-service-context.xml | ||
| Other configuration files | resources/jta.properties |
8. Domain Layer
The service layer blueprint applies to the Spring MVC, Spring WebFlow, JavaServer Faces (JSF 2.0), Adobe Flex, Google Web Toolkit (GWT), and iPhone web layer blueprints.
Item | Description | ||
| JPA Entities w/ a full set of JPA Named Queries | generated/<packageName>/Domain.java | ||
| Primary Key Classes | generated/<packageName>/DomainPK.java |
9. Persistence/DAO Layer
The service layer blueprint applies to the Spring MVC, Spring WebFlow, JavaServer Faces (JSF 2.0), Adobe Flex, Google Web Toolkit (GWT), and iPhone web layer blueprints.
Item | Description | ||
| DAO Interface | generated/<packageName>/DomainDAO.java | ||
| Spring Repository (@Repository) | generated/<packageName>/DomainDAOImpl.java | ||
| Fully implemented persistence methods | |||
| JUnit tests | one test per DAO functiongenerated/<packageName>/DomainDAOTest.java | ||
| Spring context file for DAO layer | resources/projectname-dao-context.xml | ||
| Other configuration files |
|