https://bz.apache.org/bugzilla/show_bug.cgi?id=65436

            Bug ID: 65436
           Summary: Wrong behavior observed when modifiying a custom
                    property in an MS Word 2003 .doc file (Using POI
                    4.0.1) after the same custom property was earlier
                    modified using POI 3.15
           Product: POI
           Version: unspecified
          Hardware: PC
            Status: NEW
          Severity: major
          Priority: P2
         Component: POI Overall
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

Created attachment 37946
  --> https://bz.apache.org/bugzilla/attachment.cgi?id=37946&action=edit
This contains the code referred in this bug and the attached video

Steps to reproduce
-------------------

1. Create an MS Word 2003 .doc file and name it as test.doc. 
2. In the test.doc file create a text custom property "r_version_label". Give
it a value 0.2
3. Using POI 3.15 library modify this custom property and give it a value of
0.3 (Java program attached "Test_POI_315.java" inside test-poi.zip)
        - Modify the dependency in the pom.xml to use poi 3.15 library
4. Using POI 4.0.1 library modify the custom property again and give it a value
0.4 (Java program attached "Test_POI_401.java" inside test-poi.zip)
        - Modify the dependency in the pom.xml to use poi 4.0.1 library
5. Then open the file and view its custom property value.

Expected Result 
- The custom property value should be 0.4 

Actual Result
- The custom property value is 0.


Attachments
1. test-poi.zip (contains pom.xml to switch between poi 3.15 and 4.0.1, one
java program to use for each version. Two programs created as there is an API
difference between the two versions)
2. Screen-recording demonstrating the same behavior.

-- 
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to