Yes, I have it happening on  I have a select box pointing at a 
Integer like this:  I am using the rest 
plugin which is including it in the stack.  I have attached the source from 
Maven.  Where is the check being done in the code?  I see the check for 
shouldAddError() always returning true.

I have attempted to override the default interceptor by adding this in my 
package and overriding the shouldAddError(), but it continues to call the 
default Struts ConversionErrorInterceptor.

<interceptor name="conversionError" 

Paul R. Zepernick
Sr. Programmer Analyst
HealthSmart Benefit Solutions

-----Original Message-----
From: Yasser Zamani [] On Behalf Of Yasser Zamani
Sent: Wednesday, February 14, 2018 4:25 AM
Subject: Re: Conversion Error Interceptor prevent errors for empty values

On 2/13/2018 8:06 PM, Paul Zepernick wrote:
> Can someone provide some clarification on if this interceptor should be 
> adding a field error when an empty string is passed to a Integer in the 
> action?

No, it should not be happening for `conversionError` interceptor. Does it 

>   I am trying to prevent the field error from happening in this case.  It 
> looks like it should not be happening according to the docs: 
> , 
> or am I not understanding what it is saying here:
> "This interceptor extends ConversionErrorInterceptor but only adds conversion 
> errors from the ActionContext to the field errors of the action if the field 
> value is not null, "", or {""} (a size 1 String array with only an empty 
> String). See ConversionErrorInterceptor for more information, as well as the 
> Type Conversion documentation"

You understood correctly. I reviewed it's code and looks like it should behave 
as above. Doesn't it?

I also saw `conversionError` is already included in default stack.

To unsubscribe, e-mail:
For additional commands, e-mail:

Disclaimer: This communication and any files transmitted with it may contain 
information that is privileged, confidential and/or exempt from disclosure 
under applicable law. If you are not the intended recipient, you are hereby 
notified that any disclosure, copying, distribution, or use of the information 
contained herein (including any reliance thereon) is strictly prohibited. If 
you received this communication in error, please immediately contact the sender 
and destroy the material in its entirety, whether in electronic or hard copy 
format. Thank you.

To unsubscribe, e-mail:
For additional commands, e-mail:

Reply via email to