It is not practical to allow hardcoding of HTTP related parameters such as keystore password etc. so the best approach is passing in the config file. For OSGi mode, the Netty transport bundle will look for the transport config file in the default path and load it if found.
On Wed, Feb 24, 2016 at 12:28 PM, Asanka Vithanage <[email protected]> wrote: > Hi All, > > Currently if we need to enable HTTPS for micro service [in fat jar mode] > we should define it on a netty-transports.yml file and run the jar file > with define configuration. check the doc [1]. > > I believe we should provide both HTTP and HTTPS inbuilt support in fat > jar mode.Since current way supporting HTTPS is not much user friendly. Do > we have an any technical limitation in providing this support? WDYT? > > Further we don't have any documentation or sample which explains how to > enable HTTPS on osgi mode as well. > > [1] > https://docs.wso2.com/display/MSF4J100/Invoking+Your+Microservice+via+HTTPS > > -- > Asanka Vithanage > Senior Software Engineer -QA > Mobile: +94 0716286708 > Email: [email protected] > WSO2 Inc. www.wso2.com > > -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>* *email: **[email protected]* <[email protected]> * cell: +94 77 3320919blog: **http://blog.afkham.org* <http://blog.afkham.org> *twitter: **http://twitter.com/afkham_azeez* <http://twitter.com/afkham_azeez> *linked-in: **http://lk.linkedin.com/in/afkhamazeez <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
