[jira] [Resolved] (WICKET-5217) Introduce interfaces for base wicket objects and use them in API.

["Martin Grigorov (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-5217.
-------------------------------------

    Resolution: Won't Fix

Sorry but we cannot change the APIs of almost everything in Wicket just to make it more easier to use in testing.
Adding these interfaces and then use them in other parts of the APIs will cause a huge API change which will make the life of many applications in production very hard when the time to migrate to a newer version comes.

You can start a discussion in dev@wicket.apache.org if you think that your idea deserves more discussions.
                
> 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