Kedar,
I started working on this for Prelude. The idea is to expose the api,
exactly the way you suggetsed.
The idea is to expose
common/glassfish-api/src/main/java/org/glassfish/api/branding/Branding
interface which exposes the methods similar to current Version class.
Branding is also a contract and the Service implementation corresponding
to this interface will be avialbale thru habitat, for ex.
habitat.getByContract(Branding.class). The Branding interface will be
implemented for a distribution and made available under glassfish/modules.
Pl. let me know if you have any comments.
thanks
sreeni
Kedar Mhaswade wrote:
> In GlassFish V2, appserv-ext.jar used to contain a class,
> com.sun.appserv.util.server.Version.class. This class had
> public static methods relating the server's version. This jar
> was documented to be the public API of GlassFish V2.
>
> I see that this class is now available in v3/common/common-util.
>
> Is it going to be placed in appserv-ext.jar for v3 as well?
> At the moment, it is placed in modules/common-util-10.0-SNAPSHOT.jar,
> which I don't is a public interface of v3.
>
> Thus, is appserv-ext.jar and the above class going to remain
> a public interface in v3 as well?
>
> If yes, shouldn't this class be moved from v3/common/common-util
> to v3/common-util/glassfish-api?
>
> If not, what's the alternative?
>
> Regards,
> Kedar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>