Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 126220

Summary: not all UserImpl set methods are being called
Product: [Retired] Red Hat Network Reporter: Ryan Bloom <rbb>
Component: RHN/R&DAssignee: Ryan Bloom <rbb>
Status: CLOSED NOTABUG QA Contact: Fanny Augustin <fmoquete>
Severity: medium Docs Contact:
Priority: medium    
Version: RHN DevelCC: mmccune
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-06-18 01:08:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 125080    

Description Ryan Bloom 2004-06-17 18:14:38 UTC 
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-18 01:08:36 UTC 
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.