You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Filip S. Adamsen (JIRA)" <de...@tapestry.apache.org> on 2008/09/16 20:28:45 UTC
[jira] Updated: (TAPESTRY-2675) ComponentSource#getPage(String)
does not handle a blank page name correctly
[ https://issues.apache.org/jira/browse/TAPESTRY-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Filip S. Adamsen updated TAPESTRY-2675:
---------------------------------------
Priority: Major (was: Blocker)
This isn't as big a deal as I thought at first. I still believe something should be done, though.
> ComponentSource#getPage(String) does not handle a blank page name correctly
> ---------------------------------------------------------------------------
>
> Key: TAPESTRY-2675
> URL: https://issues.apache.org/jira/browse/TAPESTRY-2675
> Project: Tapestry
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.0.15
> Reporter: Filip S. Adamsen
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org