Hi,
I've just changed all relevant places in Wicket from AjaxRequestTarget
to IPartialPageRequestHandler.
I don't think this change is too disruptive:
- client code can still call the existing methods with an ART, e.g.
modalWindow.close(ajaxRequestTarget)
- all places needing an ART remain unchanged, e.g.
AjaxLink#onClick(AjaxRequestTarget)
- a dozen Wicket components had to be changed to cooperate with
IPartialPageRequestHandler instead of just ART:
find(IPartialPageRequestHandler.class)
If we identify other methods later, we can still broaden their signature
to use IPartialPageRequestHandler
without breaking the API.
we are very (very) close to release 7.0.0, that's why I am a little bit
concerned
So am I, but for now I think it's simpler to go one step further instead
of 2 steps back.
Regards
Sven
On 09.07.2015 00:31, Sebastien wrote:
Hi Sven,
But it seems in wicket-jquery-ui there are more methods of this kind?
True, about 85 methods (taking an ART without starting with "on"-prefix).
In these, I should identify the ones that should be changed (like #open,
#close, #show, #hide, #refresh, etc), the others, plus 2 calls to
#find(ART.class) to be taken into account...
This is a new change since -M6 and we are very (very) close to release
7.0.0, that's why I am a little bit concerned (did I wrote "worried"
previously? ;)). I hope I/we do not miss/forget something here...
Thanks & best regards,
Sebastien.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
