On Friday 14 April 2006 10:51, Paulex Yang wrote: > Soeren Strassfeld wrote: > > Ilya Neverov schrieb: > > > > Hi Ilya, > > > > just followed your link, as I understand it, the endorsed mechanism is > > only for API Classes, which > > are developed outside the JCP. This contains the org.w3c, org.xml and > > the CORBA/omg packages, but > > not internally used packages. I guess sun in some way trusts those > > library vendors to be downward > > compatible, and so not break the API. > > I guess Harmony also trusts the introduced external dependent classlib.;) > > > And as you said, the endorsed.dir is only for newer versions of > > libraries (the docs explicitly > > points to this as well), so Applications, which depend on older > > versions, would still fail. > > Jar versioning is a difficult issue in Java world (in fact more > significant on Java EE world), maybe the official solution(I mean, the > standard) is JSR-277, but we probably need to wait for Java 7 to provide > the spec and RI. Not sure if other component mechanism like OSGi has > provided good idea on this issue?
OSGi allows each "bundle" to specify which bundles it depends upon, optionally including a version spec which uses the _Java 2 Package Versioning Specification_, http://java.sun.com/j2se/1.4.2/docs/guide/versioning/index.html Chris -- Chris Gray /k/ Embedded Java Solutions BE0503765045 Embedded & Mobile Java, OSGi http://www.k-embedded-java.com/ [EMAIL PROTECTED] +32 3 216 0369 --------------------------------------------------------------------- Terms of use : http://incubator.apache.org/harmony/mailing.html To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
