I'm taking Dubbo as a pure RPC framework, so registry center is not appropriate in my case, but the ServiceConfig keeps complaining about missing registry.
Anyone could help?
Do you want to use the direct IP to connect?
@lexburner
I've used explicit-target pattern as instructed by http://dubbo.apache.org/zh-cn/docs/user/demos/explicit-target.html
So it's really unnecessary to specify registry center in my ServiceConfig, but if I drop the serviceConfig.setRegistry(registryConfig); line, Dubbo will complain about the missing registry.
java.lang.IllegalStateException: No registry config found or it's not a valid config! The registry config is: <dubbo:registry valid="false" zookeeperProtocol="false" prefix="dubbo.registry" />
at org.apache.dubbo.config.AbstractInterfaceConfig.checkRegistry(AbstractInterfaceConfig.java:162)
at org.apache.dubbo.config.ServiceConfig.checkAndUpdateSubConfigs(ServiceConfig.java:270)
at org.apache.dubbo.config.ServiceConfig.export(ServiceConfig.java:328)
at com.xxx.xxx.rpcproxy.ProxyServiceProvider.start(ProxyServiceProvider.java:1063)
at test.DubboTest.init(DubboTest.java:44)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
.......
Registry should not be a must-have config.
<dubbo:registry address="N/A"/>
Most helpful comment
Registryshould not be a must-have config.