wcy666103 commented on issue #14859:
URL: https://github.com/apache/dubbo/issues/14859#issuecomment-2458982278
> Is it possible that it is related to the combination of configuration and
programming? In my case, only the service exposure is achieved through
programming, while the rest are through configuration. The specific
configurations are as follows:
>
> ```
> <dubbo:application name="travel-wuling" owner="travel-wuling"
version="1.0.0" environment="product" >
> <dubbo:parameter key="qos.enable" value="false"/>
> </dubbo:application>
> <dubbo:registry id="registry"
address="nacos://${nacos.host}:${nacos.port}?namespace=${nacos.namespace.dubbo}-${nacos.env}&username=${nacos.username}&password=${nacos.password}"
/>
> <dubbo:protocol name="dubbo" port="${dubbo.port.prefix}185" />
> <dubbo:provider delay="-1" timeout="10000" retries="0"
loadbalance="roundrobin" />
> <dubbo:consumer check="false" />
> ```
>
> Code snippet of service exposure:
>
> ```
> ...
> ServiceConfig service = new ServiceConfig<>();
> service.setApplication(application);
> service.setRegistry(registry);
> service.setProtocol(protocol);
> service.setInterface(cls);
> service.setRef(bean);
> service.setVersion("1.0.0");
> service.export();
> ...
> ```
You can debug or print out if the configuration parameters you got
programmatically are correct.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]