heh, as always you are arguing something without trying to understading the problem! please read my initial posting to this thread to see what the problem is.

-Igor


On 2/19/06, Gili <[EMAIL PROTECTED]> wrote:

        What is the difference between using configure(DEVELOPMENT) and
invoking the following code manually in init()?

                        getResourceSettings().setResourcePollFrequency(Duration.ONE_SECOND );
                        getDebugSettings().setComponentUseCheck(true);
                        getMarkupSettings().setStripWicketTags(false);
getExceptionSettings().setUnexpectedExceptionDisplay(IExceptionSettings.SHOW_EXCEPTION_PAGE );

        As far as I can see, nothing -- the above code was copied from
Application.java: configure(configurationType, resourceFinder). That is,
configure() just sets a whole slew of settings in one shot vs setting
them individually. Are you saying that if I execute the above code in my
init() that it will somehow fail? Isn't that a problem in its own right?

Gili

Igor Vaynberg wrote:
> because in this situation it makes sense to have this particular setting
> configued externally outside of code so that you can deploy your app and
> not have to recompile it just because now you are running in production!
>
> -Igor
>
>
> On 2/19/06, *Gili* < [EMAIL PROTECTED]
> <mailto:[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
>     <http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 >
>     _______________________________________________
>     Wicket-user mailing list
>     Wicket-user@lists.sourceforge.net
>     <mailto: Wicket-user@lists.sourceforge.net>
>     https://lists.sourceforge.net/lists/listinfo/wicket-user
>
>

--
http://www.desktopbeautifier.com/


-------------------------------------------------------
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

Reply via email to