Created attachment 411644 [details] screenshot showing the issue The File Name, SHA256, and Owner fields are blank, and the File Size field is incorrect (it's 0, rather than the actual file size). See attached screenshot. To reproduce, create a new WAR child Resource via RHQ, then go to that WAR Resource's Content>Deployed subtab.
This issue is a bit bigger than initially thought: i) fields are invalid because agent side discovery had no way of mapping .war/.ear contents to specific RHQ PackageVersion instances. ii) Some of the gui data was being pulled from incorrect places iii) UI input fields for versioning were missing when inserting initial content instance. iv) Merge was not sufficiently connecting discovered and existing definitions. The fix: i)Modify the discovery plugin element to additionally calculate package digests and update the newly discovered resources report returned. ii)Modify the client side UI elements to take versioning details and to calculate package versioning information from the uploaded file elements. iii)Modify the content discovery merge to lookup existing package version and installed package details an connect them to the discovered element information determined by the agent. Available in successful master build >= 355, with commit hash: 5db6f43e511700a4de58dace6461a81b308ecc70 and 06136ac6f6ea806c3887cf2635ab0feb6b91378a.
When testing, the content upload and deploy process is asynchronous so there is a delay before newly uploaded packages are subsequently discovered and connected to correct version information. Deploying to an appserver typicaly shows the history items in progress. For updates to installed content, the asynchronous updates and final completion is not as clear.
*** Bug 583104 has been marked as a duplicate of this bug. ***
I have verified this against the beta build jon-server-2.4.0.Beta0. I'm attaching the screenshot.
Created attachment 421221 [details] Helloworld ear file uploaded with correct information
This work was revised during the fix for 596704. See that bz for more info.
Verified this again on the 596704 environment and now the version shows as sha256. It shows a long sting for my app, but that's just mine. Marking this bug as verified. Also, attached the screenshot.
Created attachment 422029 [details] testing after bug 596704
The sha256 is being set as the version, that is the correct behavior for an app that was not assigned a version manually (during, say, a Create New or Content update) and also does not have a manifest file including version information inside.
Mass-closure of verified bugs against JON.