The map file has been updated for the following Bug changes:
+ Bug 244468. Support reading extension registry in any locale (FIXED)
+ Bug 259643. LocalFileNatives.internalSetFileInfo only sets exec bit for
owner. (ASSIGNED)
+ Bug 294429. OutOfMemoryError during workspace refresh due to FileInfo
David,
While Thomas's suggestion is absolutely correct, I think you need to step
back from the problem a little and ask if this is the right approach.
If your consumer bundle needs the Interface1 service then it should simply
bind to an instance of Interface1. If it also needs the Interface2
The map file has been updated for the following Bug changes:
+ Bug 244468. Support reading extension registry in any locale (FIXED)
+ Bug 275379. [launcher] Native Launcher looks for shared library in nl
fragment (FIXED)
+ Bug 291919. [launcher] return different error codes when failing to start
Neil,
one concrete example where the services need to be provided as a unit is the
support for JTA (coming in the Enterprise Profile soon). In the JTA case, the
provider is mandated to implement 3 services and register them, among them
UserTransaction and TransactionManager. Since they come
Hi Neil,
Thank you for your answer,
I agree with you, in the final deployment, I should not be able to get two
interfaces from the same object because in this case it would better to merge
them in another interface3 as you said, I just wanted to ask the different ways
to do that.
