You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Jeremy Thomerson (JIRA)" <ji...@apache.org> on 2010/12/20 07:47:10 UTC
[jira] Updated: (WICKET-3179) Default Component Behaviors
[ https://issues.apache.org/jira/browse/WICKET-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Thomerson updated WICKET-3179:
-------------------------------------
Fix Version/s: (was: 1.5-M4)
(was: 1.4.14)
Removing fix versions on things that were marked as fixVersion = (1.4.14 || 1.5-M4), but also weren't fixed (marked "not a problem", "won't fix", etc) so that they don't show up in release notes when in reality they weren't part of the release.
> Default Component Behaviors
> ---------------------------
>
> Key: WICKET-3179
> URL: https://issues.apache.org/jira/browse/WICKET-3179
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4.13
> Environment: Java 1.6, Windows.
> Reporter: Jean-Francois Larouche
> Priority: Minor
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> Weve got a little problem and i dont know if theres another way to do this. Ive searched and found nothing.
> We need to add some sort of ErrorBehavior to all of our form components. And the code duplication starts to be very ugly.
> Would this be possible/make sense:
> When the components renders, they call getBehaviors();
> getBehaviors() could then not only get the Component one but also call
> Application.get().getDefaultComponentBehavior(); and return the merged list.
> This does not affect anything in current wicket implementation.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.