[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Re: [osgi-dev] Interoperability problems...

I have removed osgi-dev from the cc.

There is an eclipse bug tracking this issue now: 
https://bugs.eclipse.org/bugs/show_bug.cgi?id=178477

Lets move futher relavent discussion there.

BJ Hargrave
Senior Technical Staff Member, IBM
OSGi Fellow and CTO of the OSGi Alliance
hargrave@xxxxxxxxxx

office: +1 386 848 1781
mobile: +1 386 848 3788




"Neil Bartlett" <njbartlett@xxxxxxxxx> 
Sent by: equinox-dev-bounces@xxxxxxxxxxx
03/21/2007 10:42 AM
Please respond to
Equinox development mailing list <equinox-dev@xxxxxxxxxxx>


To
"OSGi Developer Mail List" <osgi-dev@xxxxxxxxxxxxx>
cc
equinox-dev@xxxxxxxxxxx
Subject
[equinox-dev] Re: [osgi-dev] Interoperability problems...






Jim,

Sorry for not being clear with my terminology. I perhaps should have said
"not broken" rather than "compliant".

My point goes back to Niclas' original problem with his customers, who
produce bundles that are broken (e.g. missing some Import-Package) and yet
they believe they are not broken because they work on Equinox, which they
have been told is the Reference Implementation. When those bundles are
then run on Knopflerfish or Felix and they do not work, the developer
assumes Knopflerfish and Felix are broken, rather than his bundle.

However if, as Tom tells us, Equinox is only the RI when downloaded from
the Alliance and configured according to the Alliance's instructions,
surely Niclas simply needs to recommend to his customers that they first
test their bundles _on that RI_ before assuming they will be portable to
other OSGi implementations.

Regards,
Neil


> I am confused by this question.... Please clarify...
>
> A bundle that is implementing an OSGi service and wants to claim
> compatibility with the spec, needs to run the compatibiltiy kit.
>
> A bundle that implments some service "on top of" an OSGi spec has no 
OSGi
> "compatibility" opportunity, as there is no OSGi spec to be compatiblie
> with.   Hence, there is no need for an RI, but simply an implementation 
of
> a "compatibile" runtime (e.g. Equinox).
>
> What am I missing here?
>
> jim.
> ________________________________________
> Jim Colson, Chief Architect - IBM Client Software
> Distinguished Engineer
> IBM Academy of Technology
> Board Member - IT Architect Certification
>
> 11501 Burnet Rd. Austin, TX 78758
> Ph 512-823-7357, Fax 512-838-0962
> email: jccolson@xxxxxxxxxx
>
> Admin:  Christine Willis 512-838-3667
> email:  Christine_Willis@xxxxxxxxxx




             "Neil Bartlett"
             <njbartlett@gmail
             .com>                                                      To
             Sent by:                  "OSGi Developer Mail List"
             equinox-dev-bounc         <osgi-dev@xxxxxxxxxxxxx>
             es@xxxxxxxxxxx                                             cc
                                       equinox-dev@xxxxxxxxxxx
                                                                   Subject
             03/21/2007 09:07          [equinox-dev] Re: [osgi-dev]
             AM                        Interoperability problems...


             Please respond to
                  Equinox
                development
               mailing list
             <equinox-dev@ecli
                 pse.org>






This is a subtle point which I had missed the importance of until now. It
implies that all OSGi developers, if they wish to ensure their bundles are
strictly compliant, must test against the RI downloaded from the OSGi
Alliance. In particular, a bundle tested against a copy of Equinox
downloaded from eclipse.org cannot necessarily be assumed to be compliant.

In light of this, could somebody tell me where on the OSGi Alliance
website (OUTSIDE the member area) I can download the RI?

Thanks,
Neil

> The RI shipped by the OSGi Alliance is configured to be a strict OSGi
> Framework.  To launch the official RI from OSGi you must follow the
> instructions provided by the OSGi Alliance.  That will give you a strict
> OSGi Framework.  Changing Equinox to default to a strict OSGi Framework
> and then force Eclipse to configure it for its needs will cause issues
for
> all Eclipse clients and applications.  All of the Eclipse
> clients/applications will have to be reconfigured when they are upgraded
> to the latest Equinox that is now strict.  That is something I'm sure 
the
> Eclipse community would not enjoy.
>
> Tom

_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev

Download this as a file


_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev