Besides how much legacy code is there really in the default package? I cannot imagine that there is much at all since it is an open ended package without any name.
BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [EMAIL PROTECTED] Office: +1 407 849 9117 Mobile: +1 386 848 3788 "Richard S. Hall" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 09/14/2006 05:33 PM Please respond to OSGi Developer Mail List <[EMAIL PROTECTED]> To OSGi Developer Mail List <[EMAIL PROTECTED]> cc Subject Re: [osgi-dev] Strange question... John Wells wrote: > But being able to handle legacy code *does* seem like a good enough > reason to "bloat" the framework a little. This can't possibly be much > "bloat" and the use case of legacy code is compelling IMO. > Not that I don't understand, because I do. But making the OSGi framework support every ugly thing that every legacy application has ever done is not good in my book. We have used this reason to introduce some of the many things already in OSGi, some of which I think are quite ugly...there is no end to this path, we can always find another legacy issue that cannot be done. Where do we draw the line? Everyone feels that their legacy ugliness isn't so ugly. :-) -> richard > > John Wells (Aziz) > [EMAIL PROTECTED] > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Richard S. > Hall > Sent: Thursday, September 14, 2006 12:18 PM > To: OSGi Developer Mail List > Subject: Re: [osgi-dev] Strange question... > > Thomas Watson wrote: > >> As far as being able to distiguish between the different default >> packages ... is this not the same issue as having muliple versions of >> a normal package? You need to use matching attributes to distinguish >> the different packages >> > > No, this is not the same at all. Different versions have some > chronological relationship and are potentially substitutable for each > other. This is not the case at all for the default package. > > However, I agree that you could concoct a scheme that forced people to > use BSN and version with "." and that would probably work, but would be > totally brittle and doesn't seem like a good reason to further bloat the > framework. > > -> richard > >> For example: >> >> Export-Package: .;legacy-lib-name="abc";version="1.0" >> >> Export-Package: .;legacy-lib-name="xyz";version="1.0" >> >> Import-Package: .;legacy-lib-name="abc";version="1.0" >> >> Import-Package: .;legacy-lib-name="xyz";version="1.0" >> >> This allows you to pick the default package from either the abc or xyz >> > > >> legacy library. >> >> Tom >> >> >>> Can't do it. >>> >>> There is no way to express the default package in OSGi...the main >>> >> reason >> >>> is there would be no way to distinguish one bundle's default package >>> > > >>> with another's. And you couldn't just combine them all, since this >>> >> would >> >>> lead to naming conflicts. >>> >>> -> richard >>> >>> John Wells wrote: >>> >>>> How do I export the "root" package? In otherwords, a package with >>>> > > >>>> no name. I know, I know, it isn't too smart... but I'm dealing >>>> with >>>> >> legacy >> >>>> code here... >>>> >>>> Any idea? >>>> >>>> John Wells (Aziz) >>>> [EMAIL PROTECTED] >>>> >>>> >>>>>> Register now for BEA World 2006 --- See >>>>>> >> http://www.bea.com/beaworld<< >> >>>>>> >>>>>> >> ______________________________________________________________________ >> _ >> >>>> Notice: This email message, together with any attachments, may >>>> >> contain >> >>>> information of BEA Systems, Inc., its subsidiaries and >>>> >> affiliated >> >>>> entities, that may be confidential, proprietary, copyrighted >>>> >> and/or >> >>>> legally privileged, and is intended solely for the use of the >>>> >> individual >> >>>> or entity named in this message. If you are not the intended >>>> >> recipient, >> >>>> and have received this message in error, please immediately return >>>> >> this >> >>>> by email and then delete it. >>>> _______________________________________________ >>>> osgi-dev mailing list >>>> osgi-dev@bundles.osgi.org >>>> http://bundles.osgi.org/mailman/listinfo/osgi-dev >>>> >>>> >>> _______________________________________________ >>> osgi-dev mailing list >>> osgi-dev@bundles.osgi.org >>> http://bundles.osgi.org/mailman/listinfo/osgi-dev >>> >> ---------------------------------------------------------------------- >> -- >> >> _______________________________________________ >> osgi-dev mailing list >> osgi-dev@bundles.osgi.org >> http://bundles.osgi.org/mailman/listinfo/osgi-dev >> >> > _______________________________________________ > osgi-dev mailing list > osgi-dev@bundles.osgi.org > http://bundles.osgi.org/mailman/listinfo/osgi-dev > >>> Register now for BEA World 2006 --- See http://www.bea.com/beaworld<< >>> > _______________________________________________________________________ > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual > or entity named in this message. If you are not the intended recipient, > and have received this message in error, please immediately return this > by email and then delete it. > _______________________________________________ > osgi-dev mailing list > osgi-dev@bundles.osgi.org > http://bundles.osgi.org/mailman/listinfo/osgi-dev > _______________________________________________ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ osgi-dev mailing list osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
