[GLASSFISH-5744] asadmin list-containers should list the spec version of the container Created: 29/Aug/08  Updated: 28/Jun/13

Status: Open
Project: glassfish
Component/s: admin
Affects Version/s: V3
Fix Version/s: future release

Type: Improvement Priority: Major
Reporter: abien Assignee: Romain Grécourt
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: other
Platform: All


Issuezilla Id: 5,744

 Description   

The output of the command asadmin list-containers looks like that in GF 3b20

Container : jpa
properties=(ContractProvider=jpa)
Container : web
properties=(ContractProvider=web)
Container : security
properties=(ContractProvider=security
Container : jruby
properties=(ContractProvider=jruby)

GF 3 is OSGI based, so potentially more than one container could be active at
the same time or activated / deactivated at runtime. There for the spec-version
should be visible in the listing. Otherwise it is hard for real world projects
to rely on certain functionality and e.g. file bugs.

The command should list something like:

Container : jpa [2.0]
properties=(ContractProvider=jpa)



 Comments   
Comment by km [ 08/May/09 ]

Sahoo, the ModuleDefinition currently does not have getSpecVersion and the
MANIFEST.MF does not have Specification-Version attribute. We need to get this
information.

I am assigning this to you so you can decide and update the API so I can call it
from list-containers. Assign it to me when you are done.

Comment by km [ 27/May/09 ]

The right sahoo.

Comment by Tom Mueller [ 25/Jan/11 ]

Cleared the Fix version field since this issue isn't going to be fixed in V3.

Comment by Sanjeeb Sahoo [ 23/Mar/11 ]

It seems like admin folks have to work with build team to have additional metadata in the runtime to provide such information.

Generated at Mon May 04 23:23:42 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.