MSF4J now supports the unified deployment.yaml approach. This is the single config file all C5 based products should be using. So you can have the relevant MSF4J config in that file and provide it to the MSF4J runtime. MSF4J knows about the msf4j.conf System property. You can point that property to the deployment.yaml file.
On Mon, Jan 8, 2018 at 7:52 PM, Asanka Abeyweera <[email protected]> wrote: > Hi all, > > I couldn't find a way to enable "https" transport in MSF4J using MSF4J > JAVA API. AFAIU we can do that only by using the listener configurations in > the netty-transports.yml. But we would prefer if we can specify the configs > in our own product related config and then provide those configs to > MicroservicesRunner. This will allow us to, > > - Use a single config file in the product improving user experience > - Use the product in an embeddable mode without using any config file. > > Appreciate your thoughts on this matter. > > -- > Asanka Abeyweera > Associate Technical Lead > WSO2 Inc. > > Phone: +94 712228648 <+94%2071%20222%208648> > Blog: a5anka.github.io > > <https://wso2.com/signature> > -- *Afkham Azeez* Senior Director, Platform 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
