Jerome cleared this up --
localhost:8080/__asadmin is just a context-root and is not related to
the __asadmin virtual server being disabled.
So the assumption below is not correct and there is no problem.
-Peter
Peter Williams wrote:
> Ok, I'm confused.
>
> When we discussed this yesterday, I understood that the admin port
> (4848) was going to be disabled. Fine by me since I send the plugin's
> HTTP commands via the http port (8080).
>
> I read this message as saying that __asadmin is being disabled,
> regardless of port, which suggests that commands of the form
> "http://localhost:8080/__asadmin/[command...]" will not work anymore.
>
> Is this correct? If so, what should I be sending instead, as this
> will be a big problem.
>
> -Peter
>
> Kedar Mhaswade wrote:
>> For V3-TP2, we are removing the http-listener named "admin-listener"
>> from default configuration. Thus, the admin console, admin CLI and
>> web-based admin requests will work only off the only http-listener
>> named http-listener-1 whose port is 8080 by default.
>>
>> As a result of this, the virtual-server named __asadmin will also
>> cease to exist in default configuration.
>>
>> Let me know if anyone sees any issues with it.
>>
>> Regards,
>> Jerome/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
>