before your init is called.>>> Frank>>>>>>>>>>>> On 9/1/06, Korbinian Bachl <
[EMAIL PROTECTED]> wrote:>>>> it has to be in the init() function of the Application Class - the thing>> you>>>> write is deprecated in
1.2 already, and not
far as i know, the only place now to configure in 2.0 will be the
>> init() or the web.xml - rest will be regarded as error...
>>> Regards
>>>
>>>
>>> ____________
>> Von: [EMAIL PROTECTED]
>> [mailto:[EMAIL PROTECTED] Im
>&
) or the web.xml - rest will be regarded as error...
> >
> > Regards
> >
> >
> >
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Im
> Auftrag von Frank Bille
> > Gesendet: Freitag, 1. September 2006 12:27
> >
> &g
Thank you all for your comments. Now I set the configuration in
Application.init. I was jutst wondering about seeing the "You are in
DEVELOPMENT mode" during deployment, what breaks our deployment checker wich
reports an error if the deploy,ment ready application still reports "You are in
DEVEL
the web.xml - rest will be regarded as
error...
Regards
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] Im Auftrag von Frank
BilleGesendet: Freitag, 1. September 2006 12:27An:
wicket-user@lists.sourceforge.net
Betreff: Re: [Wicket-user] Wicket
2.0: You are in DEVELOPM
. September 2006 12:27An:
wicket-user@lists.sourceforge.net
Betreff: Re: [Wicket-user] Wicket
2.0: You are in DEVELOPMENT mode
Well it doesn't really matter, because your configure is the one
that counts. It's only because Application sets a default configure
(DEVELOPMENT)
Frank
BilleGesendet: Freitag, 1. September 2006 12:27An:
wicket-user@lists.sourceforge.netBetreff: Re: [Wicket-user] Wicket
2.0: You are in DEVELOPMENT mode
Well it doesn't really matter, because your configure is the one
that counts. It's only because Application sets
:
> class myapp extends WebApp{
>
> init() {
> configure(foo.bar);
> }
> }
> regards
>
> Korbinian
>
>
>
> _
>
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Im Auftrag von Stefan
> Lindner
> Gesendet: Freitag, 1. September 2006 11:44
> An:
Well it doesn't really matter, because your configure is the one that counts. It's only because Application sets a default configure (DEVELOPMENT) before your init is called. Frank
On 9/1/06, Korbinian Bachl <[EMAIL PROTECTED]> wrote:
it has to be in the init() function of the Application Class - t
] Im Auftrag von Stefan
Lindner
Gesendet: Freitag, 1. September 2006 11:44
An: wicket-user@lists.sourceforge.net
Betreff: [Wicket-user] Wicket 2.0: You are in DEVELOPMENT mode
In wicket 1.2.x it was possilbe to switch the mode in the application
construktor like
public class MyApplication
In wicket 1.2.x it was possilbe to switch the mode in the application
construktor like
public class MyApplication extends WebApplication{
public MyApplication() {
configure(Application.DEPLOYMENT);
}
now this leads tho an exception during deployment
wicket.WicketRuntimeEx
11 matches
Mail list logo
