From my perspective, it is essential to know what spec is actually
supported...
regards,
adam
Kedar Mhaswade schrieb:
>
>
> Ludovic Champenois wrote:
>> Kedar Mhaswade wrote:
>>> I had been thinking about this for quite some time, but
>>> could not get around to actually do it. At the moment,
>>> we have no support for finding out what version of
>>> Servlet/JSP or EJB or JPA ... spec a particular installation
>>> of GlassFish v3 Prelude supports. We have a "version" command
>>> that shows the product version and build ID. We also have a
>>> list-modules command that tells us the implementation versions
>>> of modules (in /modules folder). To some extent, it gives a
>>> misleading output like:
>>> Module : org.glassfish.javax.ejb:10.0.0.SNAPSHOT
>>>
>>> Isn't it desirable to have a command that identifies the
>>> spec versions a particular GlassFish Platform installation
>>> implements?
>>>
>> If we are good after Prelude, it would be possible to have a web
>> container with Servlet 2.5 and another one with Servlet 3.0, right?
>> So this version command would be per container, so we would need a
>> api to first list the set of installed containers and their
>> capabilities...
>
> See my other e-mail. How does a user know if a GlassFish installation
> implements Servlet 3.0 EA or 3.0 or JPA 1.2 or EJB 3.1 etc.?
>
> We introduced a new command in Prelude, called "list-containers", but
> I don't know if the information it presents is user friendly. Also,
> containers imply
> implementations of specs, not the spec versions themselves. [Note that
> current
> list-containers implementation depends upon Sniffers].
>
>
>