import wicket.markup.html.WebPage;
if (page instanceof WebPage)
{
((WebPage)page).beforeCallComponent(component, method);
}
.
if (page instanceof WebPage)
{
((WebPage)page).afterCallComponent(component, method);
}
Is that realy a problem? It is not a dependency to another
Regarding the newly added 'around functionality' of WebRequestCycle and WebPage.
I certainly welcome this addition in the background of Spring integration and
AOP, but I see some problems with this implementation.
First of all we now have a new dependency to HTML markup in
On 10/28/05, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Regarding the newly added 'around functionality' of WebRequestCycle and
WebPage.
I certainly welcome this addition in the background of Spring integration and
AOP, but I see some problems with this implementation.
First of all we now
Would be very nice to give it some though
But i was not talking about url generation
Just handling the component listeners (After the parsing of the url)
So pure the java side (so really the method where the talk is for now:
I was talking pure for this method:
private void invokeInterface(final
I'm fine with any changes on the short term if that makes it better
for people to use. For the longer term (1.2.), we should re-think more
about generalizing it. It's probably not difficult either, just a lot
of thinking before implementing.
Eelco
On 10/28/05, Johan Compagner [EMAIL PROTECTED]
