Bug 126220 - not all UserImpl set methods are being called
not all UserImpl set methods are being called
Status: CLOSED NOTABUG
Product: Red Hat Network
Classification: Red Hat
Component: RHN/R&D (Show other bugs)
RHN Devel
All Linux
medium Severity medium
: ---
: ---
Assigned To: Ryan Bloom
Fanny Augustin
:
Depends On:
Blocks: rhnMilestone1
  Show dependency treegraph
 
Reported: 2004-06-17 14:14 EDT by Ryan Bloom
Modified: 2007-04-18 13:09 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-06-17 21:08:36 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Ryan Bloom 2004-06-17 14:14:38 EDT
The PersistenceFactory should call all setters as a part of creating
the object, but the jcoverage report tells us that some of the setters
aren't being called.  We need to look into this.
Comment 1 Ryan Bloom 2004-06-17 21:08:36 EDT
BeanUtils is scary.  It is actually checking the old value of a
property within a bean, and if the value isn't being changed, the
setter isn't called.  I have briefly looked through the code, and I
didn't see where that check was made.  We may want to look into this.
 All of the methods that aren't getting called are trying to set a
value to null, which is the default value, so the methods aren't being
called.

Note You need to log in before you can comment on or make changes to this bug.