Bug 23977 - Change the implementation of SpecialPropertySet to set the fields
Summary: Change the implementation of SpecialPropertySet to set the fields
Status: RESOLVED LATER
Alias: None
Product: POI
Classification: Unclassified
Component: HPSF (show other bugs)
Version: 2.0-pre3
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---
Assignee: POI Developers List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-21 16:39 UTC by Robert Flaherty
Modified: 2010-06-03 12:53 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Flaherty 2003-10-21 16:39:01 UTC 
I ran into this when I derived from DocumentSummaryInformation to add a helper 
method to get the custom properties.  It may be more useful to copy the fields 
from the delegated PropertySet into the wrapped one in the constructor, and 
then there will be no need for the 'delegate' field or any overridden 
methods.  Then, anyone who derives from DocumentSummaryInfomation can add say 
their own getters to get specialized properties and freely use the fields.
Comment 1 Rainer Klute 2003-10-22 05:50:57 UTC 
Your issue is valid. However, I don't like copying field around and maintain
redundant information. I am going to implement a solution which prefers accessor
methods over direct field access.
Comment 2 Mark Thomas 2009-06-10 13:28:42 UTC 
Reset assignee so mails go to list.
Comment 3 Nick Burch 2010-06-03 12:53:26 UTC 
This bug references a very old version of POI. As no new comments have been added in a long time, I'm assuming that this bug has now been fixed

If the bug still exists with the latest version of POI, please re-open the bug and add a comment indicating this, ideally also with a failing unit test