### 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

* The interface name of the exported service
     */
    private String interfaceName;
    /**
     * The interface class of the exported service
     */
    private Class<?> interfaceClass;
    /**
     * The reference of the interface implementation
     */
    private T ref;
    /**
     * The service name
     */
    private String path;
    /**
     * The method configuration
     */
    private List<MethodConfig> methods;
    /**
     * The provider configuration
     */
    private ProviderConfig provider;
    /**
     * The providerIds
     */
    private String providerIds;
    /**
     * Whether the provider has been exported
     */