aui:input tag does not consider default value / bean value when its type is "timeZone"

• 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:
  • brazil
• Story Points: 8
• Fix Priority: 4
• Git Pull Request: https://github.com/brianchandotcom/liferay-portal/pull/20378

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

1. 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.
2. Deploy the portlet.
3. Manually add an instance of the entity above to the database.
   • The lportal.sql dump file has an entire database ready for testing.
4. Access the form to add a new entity.
5. 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.