Re: Conversion error message

2025-03-12 Thread Prasanth Pasala
Thank you. On 3/12/25 12:57 AM, Lukasz Lenart wrote: pon., 10 mar 2025 o 18:10 Prasanth napisał(a): com.opensymphony.xwork2.validator.annotations.ConversionErrorFieldValidator Are we supposed to use this annotation for a method to override the default validator? This annotation only exposes

Re: Conversion error message

2025-03-11 Thread Lukasz Lenart
pon., 10 mar 2025 o 18:10 Prasanth napisał(a): > com.opensymphony.xwork2.validator.annotations.ConversionErrorFieldValidator > Are we supposed to use this annotation for a method to override the > default validator? > This annotation only exposes any conversion errors for a given field. It doesn

Re: Conversion error message

2025-03-10 Thread Lukasz Lenart
śr., 5 mar 2025 o 16:21 Prasanth napisał(a): > They are, see below. > > Ok, that should do the trick Should I not be using > com.opensymphony.xwork2.validator.annotations.ConversionErrorFieldValidator > to set the message. This is not the class in > com.opensymphony.xwork2.validator.validators w

Re: Conversion error message

2025-03-05 Thread Prasanth
They are, see below. Should I not be using com.opensymphony.xwork2.validator.annotations.ConversionErrorFieldValidator to set the message. This is not the class in com.opensymphony.xwork2.validator.validators with the same name. Thanks, Prasanth On 3/5/25 12:37 AM, Lukasz Lenart wrote: wt.

Re: Conversion error message

2025-03-04 Thread Lukasz Lenart
wt., 4 mar 2025 o 20:35 Prasanth napisał(a): > I have the below line in the Action.properties file and it in the > WEB-INF/classes folder in the sample package as the actual action class. But > I am getting the standard error message rather than > the custom one. The file must be in the sam

Re: Conversion error message

2025-03-04 Thread Prasanth
I have the below line in the Action.properties file and it in the WEB-INF/classes folder in the sample package as the actual action class. But I am getting the standard error message rather than the custom one. invalid.fieldvalue.retirementDate=Invalid date format. Please use MM/dd/. Th

Re: Conversion error message

2025-03-04 Thread Prasanth Pasala
I will try the xxxAction.properties file.  So @ConversionErrorFieldValidator is not an annotation to replace the xxxAction-validation.xml where we can specify the different validations we need and the corresponding messages? Thanks, Prasanth On 3/4/25 9:44 AM, Lukasz Lenart wrote: pon., 3 mar

Re: Conversion error message

2025-03-04 Thread Lukasz Lenart
pon., 3 mar 2025 o 23:32 Prasanth napisał(a): > > Hi, > > I have a custom message for conversion error as below. But the webpage is > showing this and the default struts message. How do I suppress the struts > default message? I am using Struts 6.7.0 > > @ConversionErrorFieldValidator(field

Conversion error message

2025-03-03 Thread Prasanth
Hi, I have a custom message for conversion error as below. But the webpage is showing this and the default struts message. How do I suppress the struts default message? I am using Struts 6.7.0     @ConversionErrorFieldValidator(fieldName = "retirementDate",  message = "Invalid date format. Pl

Re: Overriding and localizing default conversion error message

2008-06-26 Thread Jukka Välimaa
6/08, Jukka Välimaa <[EMAIL PROTECTED]> wrote: > > > From: Jukka Välimaa <[EMAIL PROTECTED]> > > Subject: Overriding and localizing default conversion error message > > To: "Struts Users Mailing List" > > Date: Thursday, June 26, 2008, 8:40 AM > &

Re: Overriding and localizing default conversion error message

2008-06-26 Thread Dave Newton
> > Subject: Overriding and localizing default conversion error message > To: "Struts Users Mailing List" > Date: Thursday, June 26, 2008, 8:40 AM > Hi all, > > Does anybody know of a way to override the default type > conversion error of > Struts 2 in a way t

Overriding and localizing default conversion error message

2008-06-26 Thread Jukka Välimaa
Hi all, Does anybody know of a way to override the default type conversion error of Struts 2 in a way that makes it possible to localize the field name? I've tried using ${getText(fieldName)} and {0] in the overriding message, but they don't seem to work. Jukka

Re: How to change automatic type conversion error message

2008-05-17 Thread Arpan Debroy
It looks nice..thanks for the help.. On Fri, May 16, 2008 at 5:07 PM, Alberto A. Flores <[EMAIL PROTECTED]> wrote: > Read the section "Type Conversion Error Handling" in: > > http://struts.apache.org/2.x/docs/type-conversion.html > > You need to define an "invalid.fieldvalue." to do custom > type

Re: How to change automatic type conversion error message

2008-05-16 Thread Alberto A. Flores
Read the section "Type Conversion Error Handling" in: http://struts.apache.org/2.x/docs/type-conversion.html You need to define an "invalid.fieldvalue." to do custom type conversion error. Arpan Debroy wrote: In my application "id" attribute is int type of "Group" bean. In my JSP I have wr

How to change automatic type conversion error message

2008-05-15 Thread Arpan Debroy
In my application "id" attribute is int type of "Group" bean. In my JSP I have written like that :- Now if user puts a string into this text field, then error message come like that *invalid value for the field group.id But I want to show the error message with only "id" not "group.id". Is

Re: Struts2 conversion error message.

2007-01-03 Thread Ruimo Uno
ot;Ruimo Uno" <[EMAIL PROTECTED]> To: Sent: Wednesday, January 03, 2007 11:57 AM Subject: Struts2 conversion error message. > Hi, > > I'm evaluating Struts-2.0.1. > > The default error message for conversion error is > 'xwork.default.invalid.fieldvalue&#x

Re: Struts2 conversion error message.

2007-01-03 Thread Nuwan Chandrasoma
Hi, Yes it is possible . take a look at this tutorial http://struts.apache.org/2.x/docs/localizing-output.html Thansks, Nuwan. - Original Message - From: "Ruimo Uno" <[EMAIL PROTECTED]> To: Sent: Wednesday, January 03, 2007 11:57 AM Subject: Struts2 conversi

Struts2 conversion error message.

2007-01-03 Thread Ruimo Uno
Hi, I'm evaluating Struts-2.0.1. The default error message for conversion error is 'xwork.default.invalid.fieldvalue' and it shows something like the following message: Invalid field value for field "user.age". But the 'user.age' is confusing for end users. Moreover, it is difficult to undest