Kim Haase wrote:
> Hi, Anissa,
>
> I notice that in today's build, on the New Virtual Server and Edit
> Virtual Server pages, you are expected to specify an HTTP Listener.
>
> However, in the new Network Config pages, the name for these is now
> Network Listener (though the ones that are created by default are
> still called http-listener-1 and http-listener-2).
>
> Should the Virtual Server pages be updated to say Network Listeners
> instead of HTTP Listeners? If so, I could fix the strings.
I think we should change the word and use 'Network Listeners'.
'http-listener-1' is just the name of the Network Listener.
>
> Also, I notice that the Network Config screens (Network Listeners,
> Thread Pools, Protocols) all say "OTE: This page is not functional
> yet, please use CLI to manage <whatever>". I see from the discussion
> on glassfish-dev that the Thread Pool pages will move from here to
> directly under Configuration. Do you expect these pages (and the
> others) to change significantly or can I assume the layout will be
> pretty similar to what it is now?
>
I am going to remove the thread pool page under Network Config, and
revive the old Thread Pool page that we used to have as the node under
Config. ie, peer to Virtual Servers. The screen layout will be the
same as what we have in v3 Prelude.
The other pages under Network Config stays the same.
thanks
Anissa.
> Thanks,
> Kim
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: admin-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: admin-help_at_glassfish.dev.java.net
>