Skip to content

Release Notes 2.x

gApp JSF Web-Fragment

2.2.0 - 20-Feb-2019

Info

This generator release contains several changes and improvements. But it should not break any existing, manually written code.

Bug Description Effects on generated Files
APPJSF-310 do not generate widgetVar for components within a datatable [layout-name]_generated.xhtml now does not get a widgetVar attribute set for components inside <p:dataTable>, all modeled displays with set Type = List are affected by this
New Feature Description Effects on generated Files
APPJSF-104 Generate f:convertDateTime when Label Component is used for Date/Time/DateTime Data in a DTO [layout-name]_generated.xhtml
[layout-name]BeanExtendedCustomization.xhtml
[layout-name]Component.java
are affected by this. This happens when at least one of the page’s label components has an explicitely modeled datatype, which is accomplished by setting link DataType = date; for example.
APPJSF-105 Generate f:convertNumber when Label Component is used for numeric Data in a DTO [layout-name]_generated.xhtml
[layout-name]BeanExtendedCustomization.xhtml
[layout-name]Component.java
are affected by this. This happens when at least one of the page’s label components has an explicitely modeled datatype, which is accomplished by setting link DataType = date; for example.
APPJSF-295 Generate Support of Sorting for p:dataTable by using SortBy modeling option for display [layout-name]_generated.xhtml now has additional sortBy attributes generated when the modeling option SortBy is used for a display: link SortBy = [component name], [component name], …;.
APPJSF-316 Generate Code to check (at runtime) the Existence of an XHTML file for a Layout Variant [capability-name]MasterDataBean.xhtml now has a method ArrayList<String> getXhtmlIncludes() generated, that returns relative resource names for all [layout-name]_generated.xhtml and all layout variants of them. In the init() method of the bean that method is being used to check the presence of all required resources.
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
Task Description Effects on generated Files
APPJSF-325 Improve the Logic of getXhtmlSource() in [layout-name]BeanCustomization.java every generated file is affected by this
Improvement Description Effects on generated Files
APPJSF-237 Get rid of Developer Area &#39;xhtml.main&#39; in [layout-name].xhtml XHTML File every generated file is affected by this
APPJSF-330 Don't generate Constants in [Page-Name]Component.java Enum for Tags in "f" Namespace every generated file is affected by this
APPJSF-331 Improve the generated Logic in getConfigurationItems() in [layout-name]BeanCustomization.java all generated files are changed

2.1.3 - 18-Dec-2018

Bug Description Effects on generated Files
APPJSF-271 A modeled “toolbar” that is linked to a modeled “display” leads to the Toolbar Content not being aligned properly => could not be reproduced none
APPJSF-273 Some generated Classes are not yet serializable (e.g. Configuration, PerformanceTracker, …) all generated classes that are not yet Serializable will be changed (implements Serializable is added)

Java classes that are managed beans or are used as types for fields of managed bean classes are affected

the change doesn’t have any effect on the working of generated applications
APPJSF-274 Modeling Options disablable and optional for buttons that are contained in a toolbar don't have any Effect generated XHTML files that contain UI components (..._generated.xhtml) will be changed

[page-name]Bean.java and [page-name]BeanCustomization.java will get additional fields and methods

changes are to be expected only for pages that use toolbars that have buttons modeled that use the mentioned options
APPJSF-277 It is difficult/cumbersome to adapt the standard Text that is displayed in the generated Usage of the p:blockUI Component all Java files [page-name]BeanExtendedCustomization.java
Task Description Effects on generated Files
APPJSF-161 Improve Generation for p:commandButton that have the Purpose to reset the Page Data (XHTML Attributes immediate=true, resetValues=true) generated XHTML File that includes the ui components (..._generated.xhtml)

changes in generated code are only to expect when the related model for the page has the option ActionPurpose being set to Cancel for a button or link
Improvement Description Effects on generated Files
APPJSF-264 In the Selenium Test Step Method generate Code that gets the related Input and Assertion Data Object all abstract test classes Abstract[page-name]Test.java will be modified

there are no modeling options that have any effect on whether the code is generated or not