You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Igor Vaynberg (JIRA)" <ji...@apache.org> on 2007/03/08 05:51:24 UTC
[jira] Resolved: (WICKET-324) AjaxFormComponentUpdatingBehavior
updating other Component
[ https://issues.apache.org/jira/browse/WICKET-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-324.
----------------------------------
Resolution: Won't Fix
first its too late to do this in 1.2.x as it is now in maintenance meaning we only fix bugs
second, i dont really like this. i really do think you are better off writing your own custom behavior - we do give you the tools after all
> AjaxFormComponentUpdatingBehavior updating other Component
> ----------------------------------------------------------
>
> Key: WICKET-324
> URL: https://issues.apache.org/jira/browse/WICKET-324
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.2.5
> Environment: JDK 1.5, should work for 1.4
> Reporter: RĂ¼diger Schulz
> Priority: Minor
> Fix For: 1.2.6
>
> Attachments: AjaxFormComponentUpdatingBehavior.java
>
>
> I'd like to bind an AjaxFormComponentUpdatingBehavior to one FormComponent, and if the event fires, another FormComponent should be updated etc. I'll attach patches right away.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.