Kedar Mhaswade wrote:
> OK, I built V3 and then started the domain fine. I see that
> Grizzly comes up fine at port 8080. Then I deploy a war file like:
>
> "asadmin deploy --port 8080 foo.war", which successfully deploys.
>
> So, does it mean that the administrative commands are handled by
> the Grizzly listener at 8080, where user applications are deployed?
>
> Is this by design, or we are in process of directing asadmin commands
> to a separate Grizzly listener (usually at 4848, like we do for V2)?
>
>
> Dazed and Confused in Santa Clara :)
Why?
The admin area work needs to start on V3:). Welcome aboard.
For now, 1 single port is the easy workaround (and as a developer, I
don't mind simple things in the current prototype/implementation: no
need to understand username/password or master password in the current V3).
Ludo
>
> - Kedar
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>