Hi Richard,
On 2/22/2011 11:52 AM, Richard S. Hall wrote:
On 2/22/11 14:23, Scott Lewis wrote:
But I'm sort of wondering...why couldn't/shouldn't every
ServiceFactory be considered 'wacky'? :)
In the good old days, bundles did not register services for other
bundles, thus all service factories came from the bundle providing the
service. Such service factories typically had access to the classes
listed in objectClass, so this was not complicated. Once we added
Bundle.getBundleContext(), well, all bets were off...
Or maybe there could be some standard service property to signal the
ServiceFactory wackiness? All I'm suggesting is that for this use
case (and others), wouldn't it be better to have some simpler way to
signal this ServiceFactory wackiness...than to have a dummy bundle?
Possibly, like explicitly letting the service factory tell us if they
are class space compatible by giving them the target type from the
consumer.
Sure...seems reasonable to me.
-> richard
p.s. The Felix framework has included special treatment for service
factories since version 2.0.2 (see FELIX-1754).
Thanks! Could you please provide the full URL for 1754...and I'll check
it out (apologies...at this point I'm just too much of a Felix novice to
leave this up to my fingers).
Scott
_______________________________________________
OSGi Developer Mail List
[email protected]
https://mail.osgi.org/mailman/listinfo/osgi-dev
