-Igor
On 2/19/06, Gili <[EMAIL PROTECTED]> wrote:
I'd expect to be able to stick all my configuration stuff in init().
Why is it alright to move configure() into XML configuration and leave
the rest of the settings in init()? All I'm saying is that there should
be consistency.
Is there no way for us to make configure() work in init()? I understand
it is more work than simply removing configure(), but in my view that's
like fixing a bug by removing the feature. Just my 2 cents...
Gili
Andrew Lombardi wrote:
> +1 on this. To make the programmatic configure() work just seems like a
> lot of fluff, don't see why you'd ever need to call this during the
> app's lifecycle, only at the beginning.
-------------------------------------------------------
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&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user