[TAP5-132] ComponentSource#getPage(String) does not handle a blank page name correctly

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.15
• Fix Version/s: 5.0.16
• Assignee: Howard Lewis Ship
• Reporter: Filip S. Adamsen
• Created: 16/Sep/08 00:15
• Updated: 19/Sep/08 05:15
• Resolved: 19/Sep/08 05:15

Description

Between Tapestry 5.0.14 and 5.0.15 ComponentSource#getPage(String) was changed to not allow blank page names.

Unfortunately, Tapestry itself will sometimes provide a blank string as the logical page name. Logic that depends on ComponentSource#getPage(String) working with logical page names is therefore at risk of throwing exceptions.

The call to Defense#notBlank needs to be removed or Tapestry will have to make sure never to supply a blank string as the logical page name.