The Java RIA Framework

The model generation is quite long. It's possible to shorten it. On this page, only the quickest options are kept.

So, two things are possible:
- Generate only one GUI, e.g. the Swing one. Even if it's not the final GUI of your project, it's the fastest way to check a prototype.
- Under Eclipse(1): gererate only the java and hbm files.

Disabling a GUI generation can be achieved by commenting modules sections. To keep only the Swing GUI(2), the changes are:

- in file {project}/pom.xml, comment:

         <module>webapp</module>

- in file {project}/startup/pom.xml, comment:

    <module>wings</module>
    <module>remote</module>
    <module>flex</module>
    <module>qooxdoo</module>
 
Then launching "mvn package" will generate only the files for Swing(3).

Whenever you would like to disable a UI generation that i based on the webapp (all UIs but swing), you also have to comment out all related dependencies in the webapp module. So, for instance, if you want to disable Qooxdoo UI generation, edit {project}/webapp/pom.xml and comment out all qooxdoo related dependencies.

When working under Eclipse, it's possible to go further. After a first "mvn package", there is no need to do it again, as fas as the changes made to the project concern only the entities and components. Just launch:
- either "mvn generate-resources"(4) if the persistence layer is concerned: java class files and hbm files will be generated;
- otherwise "mvn generate-sources"(5): only the java class files will be generated.

Notes:
(1) the installation of jspresso under Eclipse is detailled here http://www.jspresso.org/page/importing-hr-sample-application-eclipse.

(2) If you are working under Eclipse, to avoid error messages about missing class dependancies, the Web App Libraries must be filled. So, at least one run of "mvn package" with all the web modules is needed.

Besides, when working with a snapshot version of jspresso, the archive files of jspresso duplicated in the project are updated only if the web modules are uncommented.

(3) By the way, you can also disable ddl script generation (that will speed up things a little bit) by disabling the "generate-ddl-script" profile: launch maven with "-P!generate-ddl-scripts" (don't forget the !).

(4) It's possible to launch it from Eclipse. Create a launch configuration for Maven with:
- Base directory: ${project_loc}
- Goals: generate-resources
- Maven Runtime: external, with version 2.2.1
On the "Refresh" tab, check the "Refresh resources upon completion." box with the option "The project containing the selected resource", and the "Recursively include sub-folders" box.
When the configuration is created, you can add it to the Run button menu: click on the Run button and go to "Organize Favorites..."

(5) If the plugin Maven Integration for Eclipse is installed, then it's available from the context menu: Run As/Maven generate-sources. Otherwise, you can proceed as above in note (4).