[
https://issues.apache.org/jira/browse/WICKET-4875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Colman updated WICKET-4875:
---------------------------------
Description:
When a panel is added by an application provided implementation of
IComponentResolver none of the AjaxLinkS work. When the same panel is added
explicitly it works fine.
I think it could be related to the change Wicket 6.x where all of the event
handling code is added to a script in the <head> section instead of being
distributed throughout the body where each AjaxLink is defined, like it was in
Wicket 1.5.
Attached is a quickstart that demonstrates the problem. It contains two
instances of 'SystemPanel'. One is added explicitly in HomePage.java and the
other is provided by the ComponentResolver.
Clicking the first link will output a message to stdout/console. Clicking the
second link will not because it's AjaxLink's onClick is not firing due to the
bug.
NOTE: attached quickstart uses port 80 not port 8080.
was:
When a panel is added by an application provided implementation of
IComponentResolver none of the AjaxLinkS work. When the same panel is added
explicitly it works fine.
I think it could be related to the change Wicket 6.x where all of the event
handling code is added to a script in the <head> section instead of being
distributed throughout the body where each AjaxLink is defined, like it was in
Wicket 1.5.
Attached is a quickstart that demonstrates the problem. It contains two
instances of 'SystemPanel'. One is added explicitly in HomePage.java and the
other is provided by the ComponentResolver.
Clicking the first link will output a message to stdout/console. Clicking the
second link will not because it's AjaxLink's onClick is not firing due to the
bug.
> AjaxLinks in Panels created by IComponentResolver do not work
> -------------------------------------------------------------
>
> Key: WICKET-4875
> URL: https://issues.apache.org/jira/browse/WICKET-4875
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.3.0
> Environment: Windows XP, Tomcat 6, JDK 1.6
> Reporter: Chris Colman
> Attachments: resolverAjaxIssue.zip
>
>
> When a panel is added by an application provided implementation of
> IComponentResolver none of the AjaxLinkS work. When the same panel is added
> explicitly it works fine.
> I think it could be related to the change Wicket 6.x where all of the event
> handling code is added to a script in the <head> section instead of being
> distributed throughout the body where each AjaxLink is defined, like it was
> in Wicket 1.5.
> Attached is a quickstart that demonstrates the problem. It contains two
> instances of 'SystemPanel'. One is added explicitly in HomePage.java and the
> other is provided by the ComponentResolver.
> Clicking the first link will output a message to stdout/console. Clicking the
> second link will not because it's AjaxLink's onClick is not firing due to the
> bug.
> NOTE: attached quickstart uses port 80 not port 8080.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
