You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Artem Morozov (JIRA)" <ji...@apache.org> on 2013/06/04 16:55:20 UTC
[jira] [Updated] (WICKET-5217) Introduce interfaces for base wicket
objects and use them in API.
[ https://issues.apache.org/jira/browse/WICKET-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Artem Morozov updated WICKET-5217:
----------------------------------
Summary: Introduce interfaces for base wicket objects and use them in API. (was: Introduce interfaces for base wicket object and use them.)
> Introduce interfaces for base wicket objects and use them in API.
> -----------------------------------------------------------------
>
> Key: WICKET-5217
> URL: https://issues.apache.org/jira/browse/WICKET-5217
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Reporter: Artem Morozov
>
> Introduce the following interfaces:
> * IComponent for Component class
> * IBehavior for Behavior
> .....
> Reason:
> There are lots of cases, where custom components/behaviour implements some custom interfaces.
> But usage of those components as interface refrences is difficult, because of wicket classes require interfaces.
> E. g.
> AjaxRequestTarget.add(Component..) <-- could be usefull adding IComponent there
> BaseWicketTester.getComponentFromLastRenderedPage(String path) <--- returns Component
> ...
> Thanks!
--
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