Stripes

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: None
• Fix Version/s: Release 1.5.1, Release 1.6
• Component/s: Formatting, Validation
• Labels:

  None

From the users mailing list...

Hi Christian,

I guess the value of the field was null when it's rendered, wasn't it?
It seems that encrypted field must have a non-null value when it is
rendered.

In my last project, I removed the field when the value is null to
workaround the issue.

<c:if test="${!empty actionBean.user.id}">
<stripes:hidden name="user.id" />
</c:if>

–
IMHO, it would be nice if null value is encrypted in the same way as
normal value because I often use the same form for both editing an
existing instance and creating a new instance (as most of you, I suppose).
Any thoughts?

Regards,
Iwao

1. 

   stripes-STS-521.patch

   06/Mar/08 12:51 AM

   0.7 kB

   Ryan Stuart

• Assignee:

  Ben Gunter

  Reporter:

  Ben Gunter

• Created:

  03/Mar/08 10:30 AM

  Updated:

  04/Jan/11 3:15 PM

  Resolved:

  15/Feb/09 12:40 PM