That's really the main one.
Eelco
On 1/15/07, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote:
please apart from web.xml config of deployment mode, any other settings
from getApplicationSettings() that can optimize wicket performance when
deploying on the internet fully
On 1/15/07, Eelco Hill
please apart from web.xml config of deployment mode, any other settings
from getApplicationSettings() that can optimize wicket performance when
deploying on the internet fully
On 1/15/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Strange error. Did you try running in deployment mode in cas
Strange error. Did you try running in deployment mode in case you weren't yet?
Eelco
On 1/15/07, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote:
> version 1.2.3
> development mode
>
>
> On 1/15/07, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
> > Which wicket version are you using? You are not run
version 1.2.3
development mode
On 1/15/07, Juergen Donnerstag <[EMAIL PROTECTED]> wrote:
Which wicket version are you using? You are not running out of open
files, do you? Are you running the application in development or
deployment mode?
Juergen
On 1/15/07, Ayodeji Aladejebi <[EMAIL PROTECTE
Which wicket version are you using? You are not running out of open
files, do you? Are you running the application in development or
deployment mode?
Juergen
On 1/15/07, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote:
> I always get this exception after a while of running my wicket
> application. It
I always get this exception after a while of running my wicket
application. It works on redeployment but suddenly just starts showing
this exception after somedays of running
WicketMessage: Exception in rendering component: [Component id =
heading, page = com.nairanet.nelx.HomePage, path =
0:adver
> The root cause for the exception is the user providing some wrong
> input: e.g. a date which is no date. What is/was the user error
> message in 1.1? Or are you saying you get the exception even if the
> input is correct?
Yes, exactly!
I get the error even when the input is correct.
--
> > You shouldn't need it, if you didn't require it in 1.1.
>
> I didn't require it in 1.1.
>
> > The input of the TextField is validated
> >
> > What is the user message you got in 1.1?
>
> Not sure what you mean by this...
The root cause for the exception is the user providing some wrong
input:
Man, I LOVE this community. Seriously, everybody is so helpful! That's
not always the case in other project. Thanks a bunch!!
> and you have an entry in YourPage.properties file for TypeValidator?
Nope. Do I need one now in 1.2? I didn't seem to need one with 1.1.
What is being validated, exact
Actually, I spoke too soon when I said that wasn't the issue...
On Wed, 2006-02-01 at 11:25 +0100, Juergen Donnerstag wrote:
> Usually you add a Validator to your form components yourself to
> validate that any value at all has been provided by the user, that it
> is an email address or a phone n
Sorry, the title was bad in my last post... Please disregard.
On Wed, 2006-02-01 at 19:00 +0900, David Leangen wrote:
> I'm upgrading to version 1.2 and am having a few transition issues.
>
> What do I need to do to get rid of this problem? I assume that
> something's changed since 1.1...
>
>
You're right. That was the issue.
Thanks!!
On Wed, 2006-02-01 at 11:25 +0100, Juergen Donnerstag wrote:
> Usually you add a Validator to your form components yourself to
> validate that any value at all has been provided by the user, that it
> is an email address or a phone number or whatever.
Usually you add a Validator to your form components yourself to
validate that any value at all has been provided by the user, that it
is an email address or a phone number or whatever. I found the core
only one situation where a TypeValidator is automatically added:
TextField(id, class). Are you do
Apparently you have an new TextField("foo", bar, Date.class) (substitute Date.class with any basic type such as Integer etc).This 'forces' a type conversion. and when the input can't be converted to Date, it will try to look up the message.
MartijnOn 2/1/06, David Leangen <[EMAIL PROTECTED]> wrote
Hi,
Looking up the inherintance tree was not done yet in 1.0. This was a
bug, but is fixed now. We plan releasing this weekend.
Regards,
Eelco
Dzenan Ridjanovic wrote:
My problem is:
Caused by: java.util.MissingResourceException: Unable to find
resource: urlForm.category.RequiredValidat
My problem is:
Caused by: java.util.MissingResourceException: Unable to find resource:
urlForm.category.RequiredValidator
All classes, html files and properties file are in the same directory.
My design is:
UrlAddPage
In constructor: add(new UrlAddForm("urlForm", new Url(), feedback));
U
16 matches
Mail list logo