[jira] Issue Comment Edited: (WICKET-3164) executeAjaxEvent in WicketTester works although Component is not enabled

["Frank Klein Koerkamp (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12931425#action_12931425 ] 

Frank Klein Koerkamp edited comment on WICKET-3164 at 11/12/10 10:47 AM:
-------------------------------------------------------------------------

executeAjaxEvent can be something like

{code}
Component component = getComponentFromLastRenderedPage(componentPath);
Component component = getComponentFromLastRenderedPage(componentPath);
TagTester tagTester = tester.getTagById(component.getMarkupId());
if(tagTester.getAttribute(event) == null) {
	throw new RuntimeException("component should be enabled to execute ajax event");
}
{code}

// other things that are happening in executeAjaxEvent

      was (Author: fkleinko):
    executeAjaxEvent can be something like

{code}
Component component = getComponentFromLastRenderedPage(componentPath);
TagTester tagTester = tester.getTagById(component.getMarkupId());
Assert.assertNotNull(tagTester.getAttribute("onblur"));
{code}

// other things that are happening in executeAjaxEvent
  
> executeAjaxEvent in WicketTester works although Component is not enabled
> ------------------------------------------------------------------------
>
>                 Key: WICKET-3164
>                 URL: https://issues.apache.org/jira/browse/WICKET-3164
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.4.10
>            Reporter: Frank Klein Koerkamp
>
> When Component is disabled the executeAjaxEvent still works. Because it's not checking if Component is enabled.
> But the event attribute is not rendered to the component if it's disabled.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.