Issue 96910 - Docx Fail to extract Embedded Objects via UNO
Summary: Docx Fail to extract Embedded Objects via UNO
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: Writer
Classification: Application
Component: programming (show other issues)
Version: OOO300m9
Hardware: PC Linux, all
: P3 Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: Oliver Specht
QA Contact:
URL:
Keywords: needmoreinfo
Depends on:
Blocks:
 
Reported: 2008-12-04 17:31 UTC by cactuscomputing
Modified: 2017-05-20 10:11 UTC (History)
2 users (show)

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

Attachments
File containing embedded object (11.32 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document)
2008-12-04 17:33 UTC, cactuscomputing 		no flags Details
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 cactuscomputing 2008-12-04 17:31:52 UTC 
I have some code that extracts OLE objects from MS Office documents. This works
fine for .doc files, but not for docx. The prblem occurs as the element names
are not retrieved. Consider: 
XTextEmbeddedObjectsSupplier oTSSupp =
(XTextEmbeddedObjectsSupplier)UnoRuntime.queryInterface(
XTextEmbeddedObjectsSupplier.class, document );
XNameAccess access = oTSSupp.getEmbeddedObjects();   
String[] names = access.getElementNames();

where msf is an XMultiServiceFactory instance and document is a XTextDocument
instance. When run on the attached docx file, the names array contains only a
single element that's zero length. This causes the subsequent extraction code to
fail with a com.sun.star.lang.IllegalArgumentException when creating the storage.
Comment 1 cactuscomputing 2008-12-04 17:33:39 UTC 
Created attachment 58520 [details]
File containing embedded object
Comment 2 eric.savary 2008-12-04 17:36:02 UTC 
Not a P1.

@JSK: please, take over.
Comment 3 cactuscomputing 2008-12-23 17:43:58 UTC 
Any idea for target milestone as this is an important bug for our customers?
Comment 4 joerg.skottke 2009-01-05 12:43:02 UTC 
API stuff -> CN, proposed target 3.1 if resources permit.
Comment 5 chne 2009-01-05 13:05:59 UTC 
cn->tl: for you
Comment 6 thomas.lange 2009-01-19 14:36:23 UTC 
Not time left to fix  this one in OO0 3.1 because of other issues.
Comment 7 Mathias_Bauer 2009-02-02 14:24:53 UTC 
Oliver, please check if this is a problem in the docx import
Comment 8 Oliver Specht 2009-09-30 09:30:16 UTC 
Target changed to 3.x
Comment 9 cactuscomputing 2010-02-16 18:10:23 UTC 
Still broken in oo 3.2
Comment 10 cactuscomputing 2011-01-27 19:35:53 UTC 
Still broken in 3.3. Note although the original bug is described in terms on the
UNO API, it impacts the document view as the OLE objects are not visible. Such
objects ARE visible in XLSX files.
Comment 11 Edwin Sharp 2014-04-09 19:18:40 UTC 
Please specify steps to reproduce bug.
Comment 12 Edwin Sharp 2014-04-23 05:41:06 UTC 
No info from author.