To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=63511
Issue #:|63511
Summary:|when default-constructing a new-style UNO service, no
|XInitialization::initialize is called
Component:|udk
Version:|680m160
Platform:|All
URL:|
OS/Version:|All
Status:|NEW
Status whiteboard:|
Keywords:|
Resolution:|
Issue type:|DEFECT
Priority:|P3
Subcomponent:|code
Assigned to:|fs
Reported by:|fs
------- Additional comments from [EMAIL PROTECTED] Thu Mar 23 01:25:18 -0800
2006 -------
Consider the following UNO service declaration:
service Foo : XFoo
{
createDefault();
createFromBar( XBar argument );
};
When implementing this service in C++, this requires implementation of the
XInitialization interface. Fine so far. However, when you construct a Foo
instance by calling createDefault, then your C++ class is just created, but no
XInitialization::initialize is called. When doing a createFromBar, then the C++
class is created, and initialize is called.
This leaves implementors of such services with a problem: After the object is
constructed, it cannot know whether it should default-initialize itself, or wait
for the real initilize call.
According to SB, we should change the code in
OSingleFactoryHelper::createInstanceWithArgumentsAndContext so that initialize
is always called, indepdent from whether the given argument array is empty.
---------------------------------------------------------------------
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]
