-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
I've some questions about the (non) sharing options of bundles in the deployment admin that is not clearly described in [1]: Suppose a bundle is already installed on the system, but not as part of a deployment package, e.g., MyLogService v1.0. If we would install a deployment package containing another version of MyLogService, say, v1.1, is this considered valid? If so, then the text of step 6 on page 334 of [1] should be changed as it suggests that *any* installed bundle should be upgraded, regardless whether it is part of the source package or not. If not, then the text of the first bullet of step 3 on page 333 of [1] should be changed as it suggests that source packages can *only* contain bundles that are either not present at all or present in the target package, missing the scenario where a bundle is present in the system, but not part of *any* deployment package. Another question is the (non) sharing of resources; section 114.2.2 of [1] clearly suggests that no sharing is allowed between deployment packages for *any* resource. For bundles we should check for symbolic name and version, but for any other resource this is up to the implementation of the customizer, or not? If so, I miss a step in section 114.8 where this verification should take place. [1] OSGi v4.3 compendium, Deployment Admin Specification v1.1 Thanks in advance, - -- Met vriendelijke groeten | Kind regards Jan Willem Janssen | Software Architect +31 631 765 814 /My world is:/ Luminis Technologies B.V. IJsselburcht 3 6825 BS Arnhem +31 88 586 46 30 http://www.luminis-technologies.com http://www.luminis.eu KvK (CoC) 09 16 28 93 BTW (VAT) NL8169.78.566.B.01 -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJP2bklAAoJEKF/mP2eHDc4pIsQALJbjeHFs/a5nTbpnnsD+3Ft iNJOQMqJpBW9CyjVI/Pyk2laZvJOt15TO6Gl0pst72xSRODHk4ZXeLQwaDnYk3Y+ iQ9oD/24AuS4N16RpfdoHc/4QeihiQEs7OuDYFI8jIS0OgMKQm9XSM5rCTzfRucO QZCkY32mjHbJa9Rtbvwr8oK86xGmw5IzR9oKsalCZaTOzPb0Hre4Tb3exlOl0Qyo y4A76HOK6RWoSdHhDqYBgnhPMrI2+CjsS1bXDTNRH/YBihrp1a0eSfGp2FBP7zZh dcIDUG7bqo0REAZoKbTU//ADSTwVO3rdyCv4yDqeaAKQEISFpXe1aTqJTOAf9sm9 wkpdT52fQko0m5IsG0XGN8MIYg31RwWOlNyCVvdbf8KJt9AS4pHFZmwc30DpyIKD o9xeLDC5J+mVPS7NrwSAyReRhoKvJEj5ldBv0yuXB7R5Glcd6/T9fYQDEh8LK/an jB5Yh43b387IPGwEFpXw/gbNycNhkVy8ld0WQ82wvSI3NI5+TMJjWt+5ofQveyj3 MtBkC08C2yUH0+gpzBZtS02aMqM8IXICd/HgFUfIfQ0c9f0KmJQwtgb6oCDfVuxY xLT80SDmYUHwOflqKeiyEXF7Q/Cjrq1+RZiFEoYY9y5S2H9TUUe4ckfTSmr0XRdz a1Zl5ZmR/Tvy+LlgndA4 =mEmO -----END PGP SIGNATURE----- _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
