Ok, so this is something we are missing in MSF4J. What we can do is introduce an MSF4JRuntimeBuilder which can be used to configure the MSF4J runtime. This is a simple change. Can you send a PR?
On Mon, Jan 8, 2018 at 11:18 PM, Asanka Abeyweera <asank...@wso2.com> wrote: > Hi Azeez, > > We are using MSF4J in a non-C5 (non-OSGI) environment. I think we could > still point msf4j.conf system property to the yaml config used in the > product and use the MSF4j namespace in the product config file. But we have > following two requirements which we think is not available in the MSF4J. > > > 1. *Capability to define a custom config name matching the actual use > of MSF4J *(e.g. admin services). For example, in the current approach, > we have to define the namespace "wso2.transport.http" in the config > file. This can be confused with the HTTP transport configs in the product. > Therefore it is better if we can use a different namespace like > "admin.service" to avoid the confusion. > 2. *Programmatically define the configurations without using a > file-based approach. *We are planning to use the product in an > embeddable manner without using any config file. For that, we need to be > able to provide the configurations programmatically without using a config > file. We could only define the port through the JAVA API (i.e. > microservicesRunner = new MicroservicesRunner(port)). > > WDYT? > > On Mon, Jan 8, 2018 at 8:41 PM, Afkham Azeez <az...@wso2.com> wrote: > >> 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 <asank...@wso2.com> >> 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: **az...@wso2.com* <az...@wso2.com> >> * cell: +94 77 3320919 <+94%2077%20332%200919>blog: * >> *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* >> > > > > -- > Asanka Abeyweera > Associate Technical Lead > WSO2 Inc. > > Phone: +94 712228648 <071%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: **az...@wso2.com* <az...@wso2.com> * 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 Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
