Issue 14406 - .com integration is borken in 644_m11
Summary: .com integration is borken in 644_m11
Status: CLOSED IRREPRODUCIBLE
Alias: None
Product: udk
Classification: Code
Component: code (show other issues)
Version: 644m11
Hardware: PC Windows 2000
: P2 Trivial (vote)
Target Milestone: ---
Assignee: jsc
QA Contact: issues@udk
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-13 10:18 UTC by ingenstans
Modified: 2003-07-02 13:07 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
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 ingenstans 2003-05-13 10:18:23 UTC 
I don't know whether this is really a UDK problem. But the windows .co 
integration doesn't work in 644_m11. Neither the examble script in the SDK nor 
an attempt to load OOO by hand from python will work. Focus switched to an OOop 
window, and then nothing happens for a while, until an error message says that 
that the program 'could not create object named "com.sun.star.ServiceManage" '

Steps to repeat: run the WriterDemo.vbs script out of the SDK
Comment 1 kay.ramme 2003-05-15 13:08:41 UTC 
Jürgen, please have a look that.
Comment 2 ingenstans 2003-05-20 21:43:35 UTC 
works in 1.1 beta 2, though: I can get a live connection using an 
interactive Python shell. The .vbs script in the SDK failed, but with 
a new error that I can't regard as too serious. It did make a proper 
com object, which it had failed to do before. So I shall mark this 
worksforme.
Comment 3 jsc 2003-07-02 13:07:59 UTC 
JSC: mark as closed