-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
The Deployment Admin specification allows resource processors to be specified in the manifest of the deployment package itself. Thus, one needs to know upfront what resource processors are to be used for what resources. Creating deployment packages is something that is typically done by tooling (for example Apache ACE). But these tools might want to verify whether the deployment package is valid _before_ supplying it to the deployment admin. One of those checks might be verifying whether all resources have a corresponding resource processor. However, the latter seems to be impossible as there is no way of distinguishing a resource processor bundle from 'normal' bundles. Wouldn't it be helpful to add an additional manifest header (for example: "Bundle-Customizer: pid.of.my.rp") for resource processors so they can be distinguished from other bundles? Or is there another way doing this? - -- 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/ iQIcBAEBAgAGBQJP2urTAAoJEKF/mP2eHDc4YTwP/12d6x1nAOqFQ4Yiy7BbTSXz otoLBsLD6noTj9uLB3/2umrzFfk8SNAIfxCHTwlC2eTj8EXgJLHmQXi4NQS5wxBu wuzI73z3J+qWRiVUcn2Mc2udfLUWvN8l6INyGW26TbADoa7H+j8r4ldavjHSp3hI foGe/NcmgQq00pdm5y/mk6SzgykxqqKbDRGGwx1FWis5oGnAACtVswaMqA5vPqQg 8RZie7008bDV26+R2L/m6Pe0tfq8iY0+LbZiNqPJ8Kw7aKz6GAmRo+6bIQWaQKIx 52wQ5LwdsWgLd2Myzf1+meenEr4EZI+FYOpscbPSxCYxsk2qQ2z5uxjPT0NFUzmJ 1xcRQ74RQRD7M/ZnTuNOXakXcujdoL1F4p85KGhVcWNIV4hlcN91jVBeo4zTv7F0 xImRkdNC7Deupw88jpM2MNrdMsNQvDOnD2V6H2+kDmU+uAm6AP5jVc6Qi5kQck4X 3lXghT8B6lmzdpi56NEfrtuocnNc6/Y9RbpAH2TVTTb7HX1QC2LlFUnB141bJRy3 Wk9NF4+hFcG3cTYQp1oXXnrT3rrVoz+sDqJk8yJuzh2ZOLPK3bQQ7rGTMDzrAglO uvAm/JIPWNhG/rNORyDR+kmVti5p+evRy05YeE1QaR+hb80nN4zcBP5dNAAteCcf BmB+hV9HgdkHAJSxWu6O =bosA -----END PGP SIGNATURE----- _______________________________________________ OSGi Developer Mail List [email protected] https://mail.osgi.org/mailman/listinfo/osgi-dev
