Justin Lee wrote:
> security-enabled is not a valid attribute for network-listener. that
> belongs on protocol.
Yes, I know. My point is why we need two attributes to start
http-listener-2 with https.
But we only need to set one attribute yesterday.
>
> Shing Wai Chan wrote:
>> Hi,
>> I notice some changes in domain.xml as follows:
>> <network-listener port="61934" *enabled="false"*
>> protocol="http-listener-2" transport="tcp" name="http-listener-2"
>> thread-pool="http-thread-pool"></network-listener>
>>
>> In order to enable http-listener-2 as https,
>> Yesterday, we have to set http-listener-2 with security-enabled=true
>> Today, we have to set http-listener-2 with security-enabled=true
>> "and" enabled=true
>>
>> Why do we want user to do set both enabled and security-enabled?
>> Should we have security-enabled=true for http-listener-2 in
>> domain.xml so that user only need to enabled=true?
>> Regards,
>> Shing Wai Chan
>>
>>
>> ---------------------------------------------------------------------
>> 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
>