I have to agree with Kedar on this....
GlassFish isn't just an App Server, anymore. There are a number of
"things" that have taken on the GlassFish brand...
And GF is already present in the classes full name. (We are talking
about org./glassfish/.embed.AppServer, right?)
Changing the name to org./glassfish/.embed.Glassfish wouldn't be as
redundant/funny as
javax.enterprise.deploy.shared.factories.DeploymentFactory (which I
think is very redundant/funny), but it would be close.
vbk
Lloyd Chambers wrote:
> Kedar,
>
> I disagree. What you are starting is Glassfish. It won't ever start
> BEA Web logic or Tomcat. It starts Glassfish.
>
> I vote for new Glassfish().
>
> Lloyd
>
> On Sep 12, 2008, at 10:11 AM, Kedar Mhaswade wrote:
>
>>
>>
>> Vivek Pandey wrote:
>>> With embedded API, we definitely want something like,
>>> GlassfishConfigurator or something like that which can be used by
>>> the users of embedded API,
>>> for example:
>>> AppServer as = new AppServer() //BTW, why did we change the name
>>> from GlassFish to AppServer?
>>
>> I don't know why, but I think this is appropriate because GlassFish
>> is a brand name and what you are starting is semantically an application
>> server.
>>
>> My 0.02 INR.
>>
>> -Kedar
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>