在配置文件中配置多个consumer，可能@DubboReference引用不到正确consumer，永远只能取列表第一个consumer使用

server.port=8083

dubbo.application.name=rpc-two-consumer
dubbo.application.owner=com.test
dubbo.application.organization=test
dubbo.application.logger=slf4j
dubbo.application.compiler=javassist
dubbo.application.qosEnable=true

#RegistryConfig
dubbo.registries.registry-rpc-one.id=registry-rpc-one
dubbo.registries.registry-rpc-one.protocol=zookeeper
dubbo.registries.registry-rpc-one.client=curator
#两个不同集群的注册中心 其中一个
dubbo.registries.registry-rpc-one.address=localhost:2181
dubbo.registries.registry-rpc-one.group=dubbo/rpc-one-server

dubbo.consumers.consumer-rpc-one.registryIds=registry-rpc-one
dubbo.consumers.consumer-rpc-one.check=true
dubbo.consumers.consumer-rpc-one.timeout=15000

#dubbo.protocols.{protocol  bean name}.id
dubbo.registries.registry-rpc-two.id=registry-rpc-two
dubbo.registries.registry-rpc-two.protocol=zookeeper
dubbo.registries.registry-rpc-two.client=curator
#两个不同集群的注册中心 其中一个
dubbo.registries.registry-rpc-two.address=localhost:2181
dubbo.registries.registry-rpc-two.group=dubbo/rpc-two-server

dubbo.consumers.consumer-rpc-two.registryIds=registry-rpc-two
dubbo.consumers.consumer-rpc-two.check=true
dubbo.consumers.consumer-rpc-two.timeout=15000









* <b>This usage is recommended</b>.<br/>
 * It is more flexible on bean methods than on implementation classes, and is more compatible with Spring.
 * <pre>
 * &#64;Configuration
 * class ProviderConfiguration {
 *
 *     &#64;Bean
 *     &#64;DubboService(group="demo")
 *     public DemoService demoServiceImpl() {
 *         return new DemoServiceImpl();
 *     }
 * }
 * </pre>
 *
 * <b>2. Using on implementation class of service:  </b>
 * <pre>
 * &#64;DubboService(group="demo")
 * public class DemoServiceImpl implements DemoService {
 *     ...
 * }
 * </pre>
 *
 * This usage causes the implementation class to rely on the Dubbo module.
 *
 *
 * @since 2.7.7
 */
@Documented
@Retention(RetentionPolicy.RUNTIME)
@Target({ElementType.TYPE, ElementType.METHOD})