Release Notes 2.x
gApp JSF Web-Application¶
2.1.0 - 20-Feb-2019¶
Info
This generator release contains several changes and improvements. But it should not break any existing, manually written code. Only APPJSF-283 might lead to manual re-work on your side, if you have explicitely modeled tests.
| Bug | Description | Effects on generated Files |
|---|---|---|
| APPJSF-283 | Naming of generated Test Classes for explicitely modeled Tests do not follow Maven Naming Conventions | all test classes now have an IT at the end of the file name, e.g. Login5TimesWrongIT.java BREAKING CHANGE for test code!!! Move manually written code to the newly generated files and remove the previously generated ones from your version control system. Use the regular expression DA-START.*\R(?!.*DA-ELSE.*) to find test classes that contain manually modified code. |
| New Feature | Description | Effects on generated Files |
|---|---|---|
| APPJSF-316 | Generate Code to check (at runtime) the Existence of an XHTML file for a Layout Variant | AppMasterDataBean.java now has a method ArrayList<String> getXhtmlIncludes() that returns all relative resource names for all [layout-name]_generated.xhtml files (and their layout variants) that are used in the application |
| APPJSF-317 | Generate Redirect to an existing Page into index.xhtml | the generated file index.xhtml is changed, it is ensured that the initially generated redirect navigates to a page that is used in the application |
| APPJSF-332 | Add Generation Support for Maven POM Files | a new generation group Maven has been added and can optionally be assigned to a software development project |
| Improvement | Description | Effects on generated Files |
|---|---|---|
| APPJSF-284 | Generate Implementation of getXhtmlSource() in AppLayoutCustomizationBean.java |
The default implementation of this method is changed. New methods getXhtmlSourceFor...() are added for each page section that is relevant for the PrimeFaces California template. Along with this, the generated default implementation of getStylesheet() is changed as well. Additional methods getStylesheetForTemplate...() are added to the file. |
| APPJSF-318 | Make PrimeFaces California being the default Template to be used (generation in AppLayoutCustomizationBean.java) | the default implementation of getDefaultTemplate() is changed |
| APPJSF-319 | Generate an init() Method in AppLayoutCustomizationBean.java |
an empty init() method is added |
| APPJSF-333 | Generate XHTML and Java Files to manage the common Web Page Sections 'north', 'west', etc. | new classes NorthBean.java EastBean.java SouthBean.java WestBean.java CenterBean.java ProfileMenuBean.java and new XHTML files center-north_generated.xhtml east_generated.xhtml head_generated.xhtml megamenu-name_generated.xhtml north_generated.xhtml north-left_generated.xhtml north-right_generated.xhtml route-bar_generated.xhtml sidebar-menu_generated.xhtml sidebar-profile-menu_generated.xhtml south_generated.xhtml top-menu_generated.xhtml top-profile-menu_generated.xhtml are generated |
2.0.3 - 18-Dec-2018¶
| Bug | Description | Effects on generated Files |
|---|---|---|
| APPJSF-270 | Generated Pages Menu for Developer Bar does not contain any Entry when only capabilities are assigned to an application-ui |
the generated menu XHTML file [app-name]PagesMenu_generated.xhtml in the web project will change when only capabilities were assigned to the application-ui there isn’t any productive code affected by the generator change |
| APPJSF-278 | Generated Integration Test Classes do not follow Naming Convention of Maven Failsafe Plugin, e.g. [page-name]TestIT.java | test classes are now named [page-name]TestIT.java, before their name was [page-name]Test.java BREAKING CHANGE for test code!!! Move manually written code to the newly generated files and remove the previously generated ones from your version control system. Use the regular expression DA-START.*\R(?!.*DA-ELSE.*) to find test classes that contain manually modified code. |