README revision ada1678a4262b208a7b87391f520a7767d25287c
7f007e36bec06aba6b3a0f84a64f2abf99edfcd8gsteinThis test is meant to do two things:
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj1. Verify that the weld-osgi-bundle.jar has been installed and is
2a6c49cfaef5979a5a06098f3ce987cd76769409manoj running in a GlassFish instance.
df14f0d3a5191cdd7c4bb5b03acd135d43a6f51brbb2. Verify the exported packages in the osgi bundle. It does this
df14f0d3a5191cdd7c4bb5b03acd135d43a6f51brbb by comparing the exported packages in the running bundle against
ab71b233b3a36489e44a7b061c48293be0b17788jwoolley a "golden file" (weld-osgi.properties) that contains the expected
571760de5e60c0b459cb11be45507b923cd023eejwoolley exported packages for the current release of Weld for GlassFish.
9180a5933673ffb1af633c255ceee029340f3b1erbb3. Verify that the bundle-symbolic-name is "org.jboss.weld.osgi-bundle".
2900ab946a2d76b73a14cebfe2985d253f01c967stoddardPREPARING A NEW TEST
a548c09e6a8ca1b059d0e93b5256c6ccb2b3c3cdrbbWhen a new Weld GlassFish release is done, the following must be dne:
b876b7bcf0ce3d232da723246d709e8dbbfe8762rbb1. Make sure GlassFish is started with the weld-osgi-bundle running.
35330e0d79ceb8027223bbb8330a381b1f989d6etrawick2. Use a tool (such as "bnd") to capture the exported packages in the
6f6f4a4bca281779d196acbdd5c017bb90858305trawick weld-osgi-bundle at run time. It can be found here:
bd929c73ef04789b7183b840d8db6e01d03a4d86rbb3. Put the captured exported packages information from the output
70f6f32765cfaadd6da8de6f0fea97ddd72d8fadmanoj from this tool into the metadata/weld-osgi.properties file.