Issue 86203

Summary: UserDefinedAttributes - AttributeData - name check
Product: App Dev Reporter: rvojta
Component: apiAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues, nesshof
Version: 3.3.0 or older (OOo)   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---
Description Flags
Sample document
Sample Java code none

Description rvojta 2008-02-18 17:32:05 UTC
First of all, I'm not sure if this is the right component. If not, please,
reassign it.

I accidentally found one issue, which forbids to open previously
saved file. This was done by my extension in this way ...

 - create TextTable, insert into Writer's document
 - get UserDefinedAttributes container, if there's no container, create new one
 - fill with AttributeData structures
 - set UserDefinedAttributes in TextTable

... I accidentally filled UserDefinedAttributes with one AttributeData( CDATA,
some string) with wrong name "table.column.%d.width" (without quotes). I just
forgot to format it. There was no exception, no error. I'm able to work with
this document.

But try to save this document. It works. No exception, no error. Close it and
try to reopen. dialog appears - Format error discovered in the
file in sub-document context.xml at ...

From my point of view - it's my fault. But from the user's point of view - should display similiar warning during save, so user is informed
that the document was crippled by extension (or whatever).

In other words, knows that the saved file can't be reopened and
user is not warned.
Comment 1 rvojta 2008-02-18 17:55:30 UTC
Created attachment 51576 [details]
Sample document
Comment 2 rvojta 2008-02-18 17:57:26 UTC
Created attachment 51577 [details]
Sample Java code
Comment 3 rvojta 2008-02-18 17:59:31 UTC
I just attached sample document, which was generated by (also
attached). silently saved this file, but can't reopen it.
Comment 4 jsc 2008-03-10 08:34:35 UTC
the component is correct and it is a text API issue or maybe a framework issue.
TL what do you think
Comment 5 thomas.lange 2010-07-02 07:31:30 UTC
Comment 6 thomas.lange 2010-08-20 14:21:46 UTC
tl->mst: please have a look at the exact reason and how it can be prevented. Thanks!
Comment 7 Marcus 2017-05-20 11:27:35 UTC
Reset assigne to the default "".