The same question can be asked for when host bundles become unresolved.  Do
the old attached fragments get delegated to?  The specification needs some
clarification here.

In the reference implementation the localization properties files are
cached as they are requested (but this is not required by the
specification).  When a bundle becomes unresolved then it converts to only
searching locally for new localization properties file requests but the old
cached properties values can still be used if a language is requested again
which already exists in the properties cache after a bundle becomes
unresolved.  If/When the bundle becomes resolved again then the cache is
cleared and the language files are searched again.

I opened https://www2.osgi.org/members/bugzilla/show_bug.cgi?id=570 against
OSGi to clarify.

Tom




                                                                       
  From:       Alan Cabrera <[EMAIL PROTECTED]>                       
                                                                       
  To:         OSGi Developer Mail List <[email protected]>        
                                                                       
  Date:       10/07/2007 01:30 AM                                      
                                                                       
  Subject:    Re: [osgi-dev] Finding Localization Entries              
                                                                       





Another question along a similar vein.  What happens to getHeaders()
when a fragment gets unresolved?  It didn't seem to clear in the
spec, unless I missed something.  I'm guessing that it delegates to
it's old host but maybe it could just serve up headers using what
ever l10n entries it could find locally.

Regards,
Alan

On Oct 2, 2007, at 5:42 AM, BJ Hargrave wrote:

> :-)
>
> During R4 spec development we allowed fragments to attach to multiple
> hosts. Prior to going final on R4, we changed course and limited
> fragments
> to only attach to a single host. The sentence you quote is left
> over from
> when we considered allowing fragments to attach to multiple hosts.
> Also
> see the method signature of PackageAdmin.getHosts where the return
> type is
> an array and not a scalar.
>
> We are currently discussing revisiting that decision. That is, to
> potentially allow a fragment to attach to multiple hosts. It would be
> useful to get input from the OSGi community on the pros and cons of
> such a
> change.
> From:
> Alan Cabrera
> Hello,
>
> I'm trying to get my head around 3.10.1 Finding Localization
> Entries.  The last sentence of the first paragraph confuses me.
>
> "Fragment bundles must delegate the search for a localization entry
> to their host bundle with the lowest bundle ID."
>
> Does this mean that fragment bundles can have multiple hosts?
>
>
> Regards,
> Alan
_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev

<<inline: graycol.gif>>

<<inline: ecblank.gif>>

_______________________________________________
OSGi Developer Mail List
[email protected]
http://www2.osgi.org/mailman/listinfo/osgi-dev

Reply via email to