Running "java -jar" is not embedded. Embedded is when you start V3
inside your own running JVM. There is a different API for embedded.
java -jar is a simple way to start V3. You don't get any
launcher-support this way (jvm-options, token substitution, etc .)
I'm also thinking that no user of server-instances would want to start
it that way...
The reason it came up is that the V3 bootstrap has to know *what* it is
starting. If instances are always started via asadmin it will be easy.
If java -jar is supported then it will be harder.
On 3/17/2010 4:20 PM, Dies Koper wrote:
> At last weeks meeting there was a suggestion to do the initial
> synchronization in the asadmin command (i.e. just before starting the
> instance's JVM), because the infrastructure was already there.
> I suppose that's were this question comes from?
>
> Why was "java -jar glassfish.jar" supported in the first place? Simpler
> start-up? Or to show-case embedded?
> I'd think those use-cases are not relevant for an instance in a cluster,
> so exclusively through asadmin should be fine?
>
>
> On 18/03/2010 07:32, Byron Nevins wrote:
>
>> Question: Should we support starting server-instances via "java -jar
>> glassfish.jar"? Or exclusively through an asadmin command?
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>
>
--
Byron Nevins - Sun Microsystems, Inc.
Home: 650-359-1290
Cell: 650-784-4123
Sierra: 209-295-2188