Bug 41689 - CustomProperties.setCodePage doesn't work
Summary: CustomProperties.setCodePage doesn't work
Status: RESOLVED WORKSFORME
Alias: None
Product: POI
Classification: Unclassified
Component: HPSF (show other bugs)
Version: 3.0-dev
Hardware: All All
: P4 normal (vote)
Target Milestone: ---
Assignee: POI Developers List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-23 04:18 UTC by Tim Hingeley
Modified: 2015-03-01 21:46 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 Tim Hingeley 2007-02-23 04:18:07 UTC 
Calling CustomProperties.setCodePage does not work because it appears to create a CustomProperty 
without a name, and this isn't supported by other areas of the code (such as CustomProperties.put
(CustomProperty).

The workaround is to create your own CustomProperty, set all the attributes and add it to the 
CustomProperties set with CustomProperties.put("PID_CODEPAGE", CustomProperty).
Comment 1 Nick Burch 2010-06-03 12:55:27 UTC 
This bug references a very old version of POI. Does the problem as described still apply?
Comment 2 Dominik Stadler 2015-03-01 21:46:36 UTC 
No update for a long time => closing this for now. If this is still a problem for you please verify with a recent version of POI and reopen this bug with more information, ideally a unit-test that can be used to reproduce the problem.