Strings rock man. You can defer any interpretation to a later moment.
With Strings, an authorization strategy might even decide that the
passed in String is a groovy script or something. Wouldn't that be
awesome?
On 2/10/06, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> heh, you are saying strings have advantages because annotations are limited?
> johan and i climbed out of a huge resource handling mess yesterday exactly
> because we were using strings everywhere instead of strongly typed classes.
> it was a nightmare.
>
> i dont know what the best solution is, but i dont think
>
> @AuthorizedAction("render", blah) is a nice solution.
Blame the annotation guys then. No matter how many levels of
annotations we might add, it's going to be a plain string in the end
somewhere, somehow. I would prefer to use Component.RENDER instead of
the string, but it is just not possible. Try it. Don't blame me either
for the way annotations work.
Eelco
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
Wicket-develop mailing list
Wicket-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-develop
