Jerome Dochez wrote:
>
> On Sep 2, 2008, at 1:21 PM, Bill Shannon wrote:
>
>> Kedar Mhaswade wrote:
>>> The real question I guess is whether we should try to provide an easy
>>> way to satisfy questions like: "Does my GlassFish installation
>>> support EJB 3.1"?
>>
>> Presumably that's already very clearly documented, right?
>> Can you send us a pointer to the page that documents this
>> for v3 Prelude?
>>
>> Yes, it might also be convenient to be able to answer this
>> question at runtime or via the CLI, but for most people who
>> ask this question telling them to "download and install GlassFish
>> and then run an asadmin command" is not an acceptable answer.
>>
> I thought the use case was more about asking a particular installation
> what are its current installed containers.
I'm surprised if that's the question most people are asking.
Not that we shouldn't be able to answer it... And the example wasn't
"which containers" it was "which API versions". Not every API is a
container.
>> We could provide most of this information via java.lang.Package,
>> but it suffers from the flaw that you have to load at least one
>> class in the package before you can ask the question about that
>> package. Perhaps the corresponding information is more easily
>> available using the OSGi bundle APIs? Should there be a "list-bundle"
>> command that dumps out all this information for a bundle based on
>> (e.g.) the Java package name?
> there is already such a command although I may not be complete with
> regards to the requested feature (no spec level compliance information).
Does OSGi define headers to include the spec level?