Setting Generator Options

On this last wizard page you can set options that determine how AMPA generates the Java classes.

• Add Classes to Project: Select the project within your application where the Java classes will be generated. We recommend to use the default ApplicationController project. This allows you to use the classes in application-scoped managed beans as well as in the application lifecycle methods. It is also prevents that you run into class loader issues when using the same data objects in multiple features. Each MAF feature has its own class loader, but they all share the parent class loader of the ApplicationController project.
• Data Objects Package: The Java package used by the Java classes that are generated for each data object
• Service Objects Package: The Java package used by the Java classes that are generated for each Entity CRUD service class. Such a class is generated when a data object has at least one REST resource associated.
• Overwrite Data Object Classes: If checked, AMPA will overwrite existing data object classes. If you added custom code to these classes after the previous generation, you will loose this code.
• Overwrite Service Object Classes: If checked, AMPA will overwrite existing Entity CRUD service classes. If you added custom code to these classes after the previous generation, you will loose this code. This checkbox is unchecked by default because the service class typically does not need to change when payload structures change, and this is also the class that most likely contains custom code that you added after generation.