We've been having discussions about detecting errors when service's don't exist. I just tested (against Linux) instantiating a service with a completely bogus name.
XMultiComponentFactory.createInstanceWithContext returned null. Is this a bug? Shouldn't it being throwing an exception? If it's not a bug, shouldn't this be documented in the idl? Most api's (including sun's j2sdk) will document when a null can be expected and under what circumstances.
For historical reasons, implementations of XMultiComponentFactory indeed often return null instead of throwing an exception. For backwards compatibility, we should probably not consider this a bug. But it is highly appropriate that you file an issue to clarify the documentation of XMultiComponentFactory et al (XMultiServiceFactory, XSingleComponentFactory, XSingleServiceFactory).
-Stephan
thanks, mike
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
