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

Operating System version: macOs

Java version: 1.8.0

Steps to reproduce this issue

引用dubbo-spring-boot-start-2.7.0

配置属性

dubbo:
application:
# name: ${spring.applicaiton.name}
qos-enable: false
registry:
# address: zookeeper://localhost:2181
file: ${user.home}/dubbo-cache/${dubbo.applicaiton.name}/dubbo.cache
# username: admin
# password: 123456
group: dubbo
simplified: true

或者使用：

file: ${user.home}/dubbo-cache/${spring.applicaiton.name}/dubbo.cache

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

期望生成

/user/xxxx/dubbo-cache/app名称/dubbo.cache

What do you expected from the above steps？

Actual Result

➜ dubbo-cache pwd
/Users/linzhiqiang/dubbo-cache
➜ dubbo-cache ls -lsh
total 0
0 drwxr-xr-x 4 linzhiqiang staff 128B 2 20 09:54 ${dubbo.applicaiton.name}
0 drwxr-xr-x 4 linzhiqiang staff 128B 2 19 15:17 ${spring.applicaiton.name}

实际上这个变量并没有解析。

{"ApplicationConfig":{"org.apache.dubbo.config.ApplicationConfig#0":{"architecture":null,"class":"org.apache.dubbo.config.ApplicationConfig","compiler":null,"dumpDirectory":null,"environment":null,"id":"testDaoApp","logger":null,"name":"testDaoApp","organization":null,"owner":null,"prefix":"dubbo.application","qosAcceptForeignIp":null,"qosEnable":false,"qosPort":null,"registryIds":null,"shutwait":null,"valid":true,"version":null}},"ConsumerConfig":

application.name属性是存在的。

What actually happens?

If there is an exception, please attach the exception trace:

Just put your stack trace here!

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.

Environment

Dubbo version: 2.7.8

Operating System version: ubuntu 18.04

Java version: open jdk 1.8.0_222

Steps to reproduce this issue

write two providers in different groups

<dubbo:reference
id="dealMenuFileProvider"
interface="com.jiurong.mfront.workflow.checker.file.FileProvider"
protocol="hessian"
group="g1"
lazy="false"
check="false"/>

<dubbo:reference
id="newDealMnoteFileProvider"
interface="com.jiurong.mfront.workflow.checker.file.FileProvider"
protocol="hessian"
group="g2"
lazy="false"
check="false"/>

write two consumers in different groups

<dubbo:service
interface="com.jiurong.mfront.workflow.checker.file.FileProvider"
ref="dealMenuFileProvider"
protocol="hessian"
group="g1"
/>

<dubbo:service
interface="com.jiurong.mfront.workflow.checker.file.FileProvider"
ref="newDealMnoteFileProvider"
protocol="hessian"
group="g2"
/>

invoke each consumer to see which implemention is invoked

@Autowired(required = false)
public void setFileProviders(List<FileProvider> providers) {
for (FileProvider fileProvider : providers) {
System.out.println(fileProvider.getType());
}
this.providers = providers;
}

When I use hessian or rmi protocol, the provider being invoked is always the first one, group="g1". But when I use dubbo protocol, each group is invoked one by one.

Pls. provide [GitHub address] to reproduce this issue.

Expected Result

What do you expected from the above steps？

Consomer of g2 group should invoke provider of g2 group.

Actual Result

What actually happens?

All the consomers always invoke the first provider, the g1 provider.

Possible explanation

org.apache.dubbo.rpc.protocol.dubbo.DubboProtocol class used the group parameter inside, but org.apache.dubbo.rpc.protocol.hessian.HessianProtocol did not. Is service-group only supported by dubbo protocol?