Issue 47179

Summary: XMultiComponentFactory.createInstanceWithContext returns null with non-existant service
Product: App Dev Reporter: mtraum <mtraum>
Component: apiAssignee: AOO issues mailing list <issues>
Status: CONFIRMED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: christianjunker, issues
Version: 3.3.0 or older (OOo)   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description mtraum 2005-04-11 17:30:11 UTC
After discussion on the api mailing list, it was determined that, while it would
be preferable to throw an exception here, it must be kept this way for
historical reasons.

But, this is not documented. Also, it will apparently return null under other
circumstances (although I do not know which).

This also applies to XMultiServiceFactory, XSingleComponentFactory,
XSingleServiceFactory.
Comment 1 ooo 2005-04-26 16:45:47 UTC
All we can do here is to document THAT a null value can happen, but not really, 
WHEN it can happen.  This would only be possible in the varying implementations. 
not at the interface.
Comment 2 mtraum 2005-04-27 04:35:15 UTC
Shouldn't the interface specify under what conditions an implemetation can
return a null and force implementations to comply with this specification?
Comment 3 ooo 2005-04-27 12:21:38 UTC
It should, but not afterwards. There are already implementations which handle 
this differently. That's the problem when people just blindly implement specs, 
without any feedback.  It's too late.
Comment 4 mtraum 2005-04-27 12:57:25 UTC
I understand your point. 

I look forward to seeing the null documented (as you said, that it can happen,
but not the conditions which can cause it).

Thanks,
Mike
Comment 5 christianjunker 2005-08-07 22:42:52 UTC
so should XMultiComponentFactory.idl get an update?
Comment 6 Rob Weir 2013-07-30 02:16:20 UTC
Reset assignee on issues not touched by assignee in more than 2000 days.