To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=102313
User jsc changed the following:
What |Old value |New value
================================================================================
Status|UNCONFIRMED |RESOLVED
--------------------------------------------------------------------------------
Resolution| |INVALID
--------------------------------------------------------------------------------
------- Additional comments from [email protected] Thu May 28 05:34:59 +0000
2009 -------
it could have worked in the past only per luck.
The defaultBootstrap_InitialComponentContext() is the wrong approach here. You
need a well initialized UNO environment with at least an rdb file that contains
the office types as well. UNO type information is not transported via a remote
connection (at the moment, it's on our long time wish list)
Take a look at the original DocumentLoader example. Put an rdb file in the same
location as your service (or somewhere else), create a XSimpleRegsitry object
and use ::cppu::bootstrap_InitialComponentContext( rOurOwnRegFile ) );
When you initialize an Any you should use the Any shift operators, e.g.
Sequence < ::com::sun::star::beans::PropertyValue > loadProps(1);
loadProps[0].Name = OUString::createFromAscii("UpdateDocMode");
loadProps[0].Value <<=
(sal_Int16)::com::sun::star::document::UpdateDocMode::QUIET_UPDATE;
<<= to put an value/object in an Any
>>= to extract a value from an Any
Maybe you should take also a look on the simple bootstrap mechanism. Depending
on your environment it might be also a solution.
And of course the socket connection works as expected. I don't know a version
where it didn't worked ;-)
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
