### Environment

* Dubbo version: 2.7.3
* Operating System version: CentOS7
* Java version: 1.8

### Steps to reproduce this issue

1. Set two protocal, with different "register" attribute

```xml
<dubbo:protocol name="dubbo" port="8751" register="true"  />
<dubbo:protocol name="hessian" port="8752" register="false" />
```

2. use the zookeeper registry center

```xml
<dubbo:registry address="..." file="./.dubbo_cache" />
```

3. start the server and view the provider in zkCli


### Expected Result
only the dubbo is registed

### Actual Result
the dubbo and hession protocol are registed

public String getProtocolIds() {
        return protocolIds;
    }
    public void setProtocolIds(String protocolIds) {
        this.protocolIds = protocolIds;
    }
    public String getAccesslog() {
        return accesslog;
    }
    public void setAccesslog(Boolean accesslog) {
        if (accesslog == null) {
            setAccesslog((String) null);
        } else {
            setAccesslog(String.valueOf(accesslog));
        }
    }
    public void setAccesslog(String accesslog) {
        this.accesslog = accesslog;
    }
    public Integer getExecutes() {
        return executes;
    }
    public void setExecutes(Integer executes) {
        this.executes = executes;
    }
    @Override
    @Parameter(key = SERVICE_FILTER_KEY, append = true)
    public String getFilter() {
        return super.getFilter();
    }