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?
Paul -- can you point all of us to a page that tells us which
standards (e.g. EJB, Servlet/JSP) GlassFish v3 Prelude would
have support/implementation for?
>>
>> 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. Although I agree we need to
> document it somewhere too.
+1.
And generally users don't like to be told "RTFM". That's why an admin command.
Of course, a released product should document its standard compliance
at the time of release.
>
>> 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).
I believe that's asadmin list-modules.
Also, I asked Sahoo if there is something we can do in OSGi headers
for our bundles to facilitate this info.
>