https://bz.apache.org/bugzilla/show_bug.cgi?id=65965
--- Comment #4 from [email protected] --- I failed to mention the actual impact of this problem in my prior comments... Among other things this has two significant problems that require dubious work-arounds. These problems exist not only for tables, but other places where set is called, ex. setParagraph(). 1) changes made to the entity XWPF entity after "setting" don't actually make it into the resulting document. This is due to the fact that the XML object in the document isn't associated with the XWPF object and thus any changes or modifications get applied to the XWPF object and by extension applied to its XML object are not actually part of the document's XML tree. 2) any cursors derived from the XMPF entity after "setting" aren't valid as they don't point to the correct place in the document tree. For the same reasons outlined above the cursor and any actions done on it don't produce the expected outcome as it is not pointing to the underlying document's XML tree. While I have been able to work around both of these problems mostly successfully, the state and outcomes were certainly not expected and I would assume probably would not be expected by most if not all other users. -- 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]
