Issue 93617 - Let Mozilla plugin use pipe-based uno connection.
Summary: Let Mozilla plugin use pipe-based uno connection.
Status: CLOSED FIXED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: DEV300m28
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo 3.1
Assignee: uwe.luebbers
QA Contact: issues@framework
URL:
Keywords:
Depends on:
Blocks: 72764
  Show dependency tree
 
Reported: 2008-09-08 17:20 UTC by mikhail.voytenko
Modified: 2010-02-22 14:59 UTC (History)
4 users (show)

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

Attachments
Patch to this issue (27.58 KB, text/plain)
2008-09-09 04:20 UTC, zhangxiaofei.ooo 		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 mikhail.voytenko 2008-09-08 17:20:34 UTC 
The plugin implementation should use pipe based UNO connection.
Comment 1 zhangxiaofei.ooo 2008-09-09 04:20:43 UTC 
Created attachment 56339 [details]
Patch to this issue
Comment 2 mikhail.voytenko 2008-09-09 08:55:32 UTC 
mav->zhangxiaofei: Thank you for the patch. I will integrate and test it in one
of the next framework OOo3.1 cws's.
Comment 3 mikhail.voytenko 2008-11-13 11:56:36 UTC 
Ups, the patch flag was not set.
Comment 4 mikhail.voytenko 2008-11-21 14:26:59 UTC 
integrated in fwk92
Comment 5 mikhail.voytenko 2008-11-26 10:11:12 UTC 
mav->ul: Please verify whether the plugin still works as expected.
Comment 6 mikhail.voytenko 2008-12-01 09:00:07 UTC 
mav->ul: please verify the issue
Comment 7 thorsten.martens 2008-12-09 10:59:09 UTC 
Checked and verified in cws fwk92 -> OK !
Comment 8 thorsten.ziehm 2010-02-22 14:59:25 UTC 
This issue is closed automatically. It should be fixed in a version with is
available for longer than half a year (OOo 3.1). If you think this issue isn't
fixed in the current version (OOo 3.2) please reopen it. But then please pay
attention about the field 'target milestone'.
The closure was approved by the Release Status Meeting at 22nd of February 2010
and it is based on the issue handling guideline for fixed/verified issues  :
http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues