[
https://issues.apache.org/jira/browse/WICKET-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13676256#comment-13676256
]
Cedric Gatay commented on WICKET-5217:
--------------------------------------
What is so limiting in Behavior or Component classes ? If you can narrow the
things limiting you it can help us understand your needs (IBehavior existed
before 6.x branch).
> 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
