You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Maurice Marrink (JIRA)" <ji...@apache.org> on 2008/04/29 11:49:57 UTC
[jira] Created: (WICKET-1575) AjaxEventBehavior does not check for
component.isEnableAllowed before adding the ajax event to the tag
AjaxEventBehavior does not check for component.isEnableAllowed before adding the ajax event to the tag
------------------------------------------------------------------------------------------------------
Key: WICKET-1575
URL: https://issues.apache.org/jira/browse/WICKET-1575
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.3.3, 1.3.2
Reporter: Maurice Marrink
Assignee: Maurice Marrink
Fix For: 1.3.4, 1.4-M1
Currently AjaxEventBehavior only checks component.isEnabled before applying the ajax event to the tag. This could result in an UnauthorizedActionException when the ajax event is received by wicket.
The behavior should also check for component.isEnableAllowed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-1575) AjaxEventBehavior does not check for
component.isEnableAllowed before adding the ajax event to the tag
Posted by "Maurice Marrink (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maurice Marrink updated WICKET-1575:
------------------------------------
Affects Version/s: 1.4-M1
1.3.4
Fix Version/s: (was: 1.4-M1)
1.4-M2
> AjaxEventBehavior does not check for component.isEnableAllowed before adding the ajax event to the tag
> ------------------------------------------------------------------------------------------------------
>
> Key: WICKET-1575
> URL: https://issues.apache.org/jira/browse/WICKET-1575
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.2, 1.3.3, 1.3.4, 1.4-M1
> Reporter: Maurice Marrink
> Assignee: Maurice Marrink
> Fix For: 1.3.4, 1.4-M2
>
>
> Currently AjaxEventBehavior only checks component.isEnabled before applying the ajax event to the tag. This could result in an UnauthorizedActionException when the ajax event is received by wicket.
> The behavior should also check for component.isEnableAllowed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-1575) AjaxEventBehavior does not check for
component.isEnableAllowed before adding the ajax event to the tag
Posted by "Maurice Marrink (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maurice Marrink resolved WICKET-1575.
-------------------------------------
Resolution: Fixed
> AjaxEventBehavior does not check for component.isEnableAllowed before adding the ajax event to the tag
> ------------------------------------------------------------------------------------------------------
>
> Key: WICKET-1575
> URL: https://issues.apache.org/jira/browse/WICKET-1575
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.2, 1.3.3, 1.3.4, 1.4-M1
> Reporter: Maurice Marrink
> Assignee: Maurice Marrink
> Fix For: 1.3.4, 1.4-M2
>
>
> Currently AjaxEventBehavior only checks component.isEnabled before applying the ajax event to the tag. This could result in an UnauthorizedActionException when the ajax event is received by wicket.
> The behavior should also check for component.isEnableAllowed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Reopened: (WICKET-1575) AjaxEventBehavior does not check for
component.isEnableAllowed before adding the ajax event to the tag
Posted by "Maurice Marrink (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maurice Marrink reopened WICKET-1575:
-------------------------------------
commits can't be made at this time due to infra structure problems.
> AjaxEventBehavior does not check for component.isEnableAllowed before adding the ajax event to the tag
> ------------------------------------------------------------------------------------------------------
>
> Key: WICKET-1575
> URL: https://issues.apache.org/jira/browse/WICKET-1575
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.2, 1.3.3, 1.3.4, 1.4-M1
> Reporter: Maurice Marrink
> Assignee: Maurice Marrink
> Fix For: 1.3.4, 1.4-M2
>
>
> Currently AjaxEventBehavior only checks component.isEnabled before applying the ajax event to the tag. This could result in an UnauthorizedActionException when the ajax event is received by wicket.
> The behavior should also check for component.isEnableAllowed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-1575) AjaxEventBehavior does not check for
component.isEnableAllowed before adding the ajax event to the tag
Posted by "Maurice Marrink (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-1575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maurice Marrink resolved WICKET-1575.
-------------------------------------
Resolution: Fixed
> AjaxEventBehavior does not check for component.isEnableAllowed before adding the ajax event to the tag
> ------------------------------------------------------------------------------------------------------
>
> Key: WICKET-1575
> URL: https://issues.apache.org/jira/browse/WICKET-1575
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.3.2, 1.3.3, 1.3.4, 1.4-M1
> Reporter: Maurice Marrink
> Assignee: Maurice Marrink
> Fix For: 1.3.4, 1.4-M2
>
>
> Currently AjaxEventBehavior only checks component.isEnabled before applying the ajax event to the tag. This could result in an UnauthorizedActionException when the ajax event is received by wicket.
> The behavior should also check for component.isEnableAllowed.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.