Issue 79537 - Provide an XNameContainer implementing css::xml::AttributeContainer via Service Factory
Summary: Provide an XNameContainer implementing css::xml::AttributeContainer via Servi...
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: App Dev
Classification: Unclassified
Component: api (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: bjoern.milcke
QA Contact: issues@api
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-12 14:47 UTC by bjoern.milcke
Modified: 2013-02-24 21:08 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Latest Confirmation in: ---
Developer Difficulty: ---

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

Note You need to log in before you can comment on or make changes to this issue.
Description bjoern.milcke 2007-07-12 14:47:39 UTC 
Throughout the applications we support the UserDefinedAttributes property which
is an XNameContainer with the purpose of storing unknown XML-attributes when
loading an XML file.

This property is void in chart2, which is a good thing as this saves space until
an unknown attribute is read in xmloff. The code in xmloff creates a component
locally implemented in xmloff for this purpose.

When trying to test the UserDefinedAttributeSupplier service with automated API
tests, it should be possible to create this container via service factory.
Comment 1 Martin Hollmichel 2007-11-09 17:28:14 UTC 
set target from 2.x to 3.x according to
http://wiki.services.openoffice.org/wiki/Target_3x
Comment 2 bjoern.milcke 2008-08-13 12:45:18 UTC 
Hm, I think this task is not really necessary.
Comment 3 bjoern.milcke 2008-08-13 12:45:50 UTC 
closing