Jonathan Locke jonathan.locke at gmail.com writes:
this suggestion (which is implementable in a user coderegardless of what goes
into the core) add(new ReflectionLink(myLink, myMethod))makes me wonder if
Java couldn't use a reflection notation
similar to object.class to specify Method
Eelco Hillenius eelco.hillenius at gmail.com writes:
However, as a nice alternative, I can see such a
component live in Wicket extensions.
I agree, this responds to our personnal style of coding and we don't to break
the wicket way of doing things :)
I think we would implement that and if
We thought about it and as our internal component, we were ready to implement
2)
et 3). In our case we want provide a uniform style of coding : 90% of use
cases,
the method is called on the page object. 10% left are filled by 3)
Yeah, the disadvantage of calling the page object is that it
Jonathan Locke wrote:
makes me wonder if Java couldn't use a reflection notation
I have always thought this would be a great feature. (As a side note,
how hard would it be to write an eclipse plugin that would perform
compile-time checking, but would pass a string to the compiler? Aka: new
this suggestion (which is implementable in a user coderegardless of what goes into the core) add(new ReflectionLink(myLink, myMethod))makes me wonder if Java couldn't use a reflection notation
similar to object.class to specify Method objects, like myMethod.method. then you could do this both
