This page describes the structure of JumpStart 4.0.n to 4.3.n.
Web source is in these locations:
webBusiness source is in these locations:
|---components --> .java, .tml, .properties for components eg. Layout.java, Layout.tml
|---pages --> .java, .tml, .properties for pages eg. UserSearch.java, UserSearch.tml
|---services --> .java for services eg. AppModule.java and BusinessServicesLocator.java
|---WEB-INF --> app.properties file for web application-wide messages
businessEclipse compiles the java source to bin/ and runs our Ant file exploder.xml file to copy all the necessary items to exploded/, which holds an "exploded" EAR file with this structure:
|---java --> messageDefs.properties file for business messages
|---domain --> .java for business domain (services and entities eg. SecurityFinderService and User)
|---resources --> .xml for persistence and datasource descriptors
explodedJetty runs over this exploded EAR. You can see how the exploder has been configured by displaying the project's properties and choosing Builders.
|---jumpstart.jar --> the business layer
|---jumpstart.war --> the web layer
Reference These files describe the application structure. They rarely need to change.
business/src/main/resources/META-INF/persistence.xml tells the EJB3 server how we want to persist data - the datasource name and some settings.
The only one you're likely to change is persistence.xml. See Tips for more on that.
Tapestry expects a class called AppModule to exist to describe services we want added in:
Examples Here are the pieces involved in logging in:
Here are the pieces involved in editing a user. Many are the same as for logging in:
Tapestry locates components that aren't pages a little differently. For example, the "Layout" component: