Hi Hubert,
>
> I'm was recently looking at GWS and its HTTPS support.
> I found out that user can start GWS configured to serve HTTPS
> without SSLConfig.
> This renders service unusable.
We can try to use some "default" SSLConfig, which reads SSL
configuration from System properties.
> What do you think of deprecating constructor with boolean secure
> parameter and creating one that would require SSLConfig?
IMHO it could be even more clear, if we can split GrizzlyWebServer
implementation into two: Secure and non-Secure.
But because of backwards compatibility, not sure we will want to do
that.
As for deprecating/adding constructors to GrizzlyWebServer, there are
a lot of them already, so we have to avoid doing mess there :)
WBR,
Alexey.
>
> Cheers,
> Hubert.