Issue 1:
I have searched the issues of this repository and believe that this is not a duplicate.

I have checked the FAQ of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 2.7.0-SNAPSHOT

Operating System version: Ubuntu 18.04 LTS

Java version: 1.8.0_181

Step to reproduce this issue

Making a breakpoint in the 83th line of class org.apache.dubbo.config.spring.ReferenceBean

Debugging dubbo-consumer-demo

Got an exception

java.lang.reflect.InvocationTargetException
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)
at org.apache.dubbo.config.AbstractConfig.toString(AbstractConfig.java:465)
at org.apache.dubbo.config.spring.ReferenceBean.afterPropertiesSet(ReferenceBean.java:83)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1688)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1626)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:555)
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:483)
at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:312)
at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:230)
at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:308)
at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:197)
at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:742)
at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:867)
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543)
at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:139)
at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:83)
at cn.shuaijunlan.dubbo.learning.main.Main.main(Main.java:14)
Caused by: java.lang.IllegalStateException: No such application config! Please add <dubbo:application name="..." /> to your spring config.
at org.apache.dubbo.config.AbstractInterfaceConfig.checkApplication(AbstractInterfaceConfig.java:143)
at org.apache.dubbo.config.ReferenceConfig.init(ReferenceConfig.java:280)
at org.apache.dubbo.config.ReferenceConfig.get(ReferenceConfig.java:165)
at org.apache.dubbo.config.spring.ReferenceBean.getObject(ReferenceBean.java:66)
... 20 more

Issue 2:
[✔ ] I have searched the issues of this repository and believe that this is not a duplicate.

[✔ ] I have checked the FAQ of this repository and believe that this is not a duplicate. // FAT 显示404，望修正

Environment

Dubbo version: 2.7.6+

Operating System version: macOS 10.14.5

Java version: AdoptOpenJDK（1.8.0_222）

Steps to reproduce this issue

准备 consumer 和 provider 各一个服务

启动 provider 的时候通过 "-Ddubbo.provider.tag=test" 指定标签

启动 consumer 的时候不指定 Tag 参数，即使用默认值

Expected Result

在官网文档 路由规则 最后一段是这样描述的：

request.tag未设置时，只会匹配tag为空的provider。即使集群中存在可用的服务，若 tag 不匹配也就无法调用，这与约定1不同，携带标签的请求可以降级访问到无标签的服务，但不携带标签/携带其他种类标签的请求永远无法访问到其他标签的服务。

也就是说 consumer 不指定 tag 的时候流量将不会到达 provider，因为 provider 是带了 tag 标记的

Actual Result

实际上 consumer 是可以正常调用带tag标记的provider，这与文档中的描述不一致。在 2.7.5 中没有这个问题，根据我的排查，引入这个问题是由于增加了方法 org.apache.dubbo.registry.integration.RegistryDirectory#getConsumerUrl

@Override
public URL getConsumerUrl() {
return this.overrideDirectoryUrl;
}

2.7.5版本之前使用的是抽象类方法 org.apache.dubbo.rpc.cluster.directory#getConsumerUrl

public URL getConsumerUrl() {
return consumerUrl;
}

经过 org.apache.dubbo.registry.integration.RegistryDirectory#mergeUrl 方法的处理之后，程序会把provider端的tag注入到属性 this.overrideDirectoryUrl中，因此 getConsumerUrl 方法返回的URL中就有了 tag 信息

请问这个问题是否会被修正呢？还是我们的用法不对？