The structural model of a Web project tells publishers how to compose a runtime artifact (see Figure 6.26). Power users can employ these capabilities to create many different layouts for their projects. We will start with a short description of this advanced project capability, and then give examples demonstrating its use. This nature indicates that these projects have a structural model for the modules and will support WTP tools. Technically speaking, an Eclipse project that has the Module Core Nature is a Web project. We'll use the term Web project in this book. For that reason, WTP developers sometimes also refer to these projects as flexible projects. This mapping gives you flexibility to create projects in ways that you could not do before. Publishers and WTP tools use the structural model to create J2EE artifacts. Each WTP Web project has a structural model that is used to describe how developers lay out the resources. In WTP, the developer's view of a project is captured by a model that maps the contents of the project to the runtime view. Mimicking the structures defined in the specification creates valid J2EE applications, but this is not always suitable for all development projects. The developer's view is most often modeled using the J2EE specification. The runtime view is defined by the J2EE specification. A key requirement for Web projects was to enable the separation of the two fundamental view points to help manage resources in a project, for example, the developer view and the runtime view. When the WTP project was started, the development team had long discussions on how to extend the basic Java projects to handle different styles of custom projects. Unit and integration tests are part of the development for each module. Test objectives and responsibilities are determined based on the modules.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |