[
https://issues.apache.org/jira/browse/WICKET-1929?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Dearing updated WICKET-1929:
---------------------------------
Description:
Currently newPagingNavigationLink and newPagingNavigationIncrementLink in
PagingNavigator return Link objects. It would be nice if they returned
AbstractLink objects to allow more flexibility. This would make using
SubmitLink and custom Link components with PagingNavigator much easier.
This was discussed back in Jan 08 (
http://markmail.org/message/dfgnis2rc7ysjlhj ), but I could not find a JIRA
issue for it.
For now using Behaviors may work and avoids duplicating a lot of the code.
was:
Currently newPagingNavigationLink and newPagingNavigationIncrementLink in
PagingNavigator return Link objects. It would be nice if they returned
AbstractLink objects to allow more flexibility. This would make using
SubmitLink and custom Link components with PagingNavigator much easier.
This was discussed back in Jan 08
(http://markmail.org/message/dfgnis2rc7ysjlhj), but I could not find a JIRA
issue for it.
For now using Behaviors may work and avoids duplicating a lot of the code.
> PagingNavigator.newPagingNavigationIncrementLink and
> PagingNavigator.newPagingNavigationLink should return AbstractLink
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: WICKET-1929
> URL: https://issues.apache.org/jira/browse/WICKET-1929
> Project: Wicket
> Issue Type: Improvement
> Affects Versions: 1.3.0-final, 1.3.1, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4-M1,
> 1.4-M2, 1.4-M3
> Reporter: Ryan Dearing
>
> Currently newPagingNavigationLink and newPagingNavigationIncrementLink in
> PagingNavigator return Link objects. It would be nice if they returned
> AbstractLink objects to allow more flexibility. This would make using
> SubmitLink and custom Link components with PagingNavigator much easier.
> This was discussed back in Jan 08 (
> http://markmail.org/message/dfgnis2rc7ysjlhj ), but I could not find a JIRA
> issue for it.
> For now using Behaviors may work and avoids duplicating a lot of the code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
