-
Type:
Bug
-
Status: Closed
-
Resolution: Fixed
-
Affects Version/s: 7.0.0 M3
-
Fix Version/s: 7.0.0 M1
-
Component/s: ~ [Archived] Frontend Infrastructure, ~[Archived] UI Taglibs
-
Labels:
-
Story Points:8
-
Fix Priority:4
-
Git Pull Request:
The <aui:input> tag, when used in conjunction with <aui:model-context> tag, sets its own value with the value of a bean. However, if the input is of the type "timeZone", it does not behave this way. If a instance of the bean is given, <aui:input> fails, as well as if no instance is given.
Steps to reproduce
- Create a portlet which:
- has a service whose entity has a "timeZoneId" string field (cf. service.xml
).
- has a form to create and edit such entities, using <aui:form>, <aui:model-context> and <aui:input>. The aui:input corresponding to the "timeZoneId" field should be of the type "timeZone" (cf edit_city.jsp
).
- The attached "Input Time Zone Portlet" (Eclipse project
, WAR file
) has this properties.
- has a service whose entity has a "timeZoneId" string field (cf. service.xml
- Deploy the portlet.
- Manually add an instance of the entity above to the database.
- The lportal.sql
dump file has an entire database ready for testing.
- The lportal.sql
- Access the form to add a new entity.
- Access the form to edit the entity added to the database.
Expected results
- In step 4, the time zone input should appear and the selected time zone should be the portal's default.
- In step 5, the time zone input should appear and the selected time zone should be the entity's time zone id.
Actual results
- In step 4, the time zone input does not appear. A NullPointerException stack trace appears in the logs.
- In step 5, the time zone input does not appear. A NullPointerException stack trace appears in the logs.