2.Dubbo动态扩展

最新推荐文章于 2023-07-11 22:42:48 发布

胡晗-

最新推荐文章于 2023-07-11 22:42:48 发布

阅读量2.8k

点赞数

分类专栏： dubbo 文章标签： java

本文链接：https://blog.csdn.net/phoenix9311/article/details/111470669

版权

dubbo 专栏收录该内容

2 篇文章 0 订阅

订阅专栏

我们知道dubbo通过SPI机制实现了灵活的动态扩展，但是这些扩展的优先级怎么样？怎么去判断最后采用的是哪个实现？

先上结论：@Adaptive注解实现类 > 配置名对应的实现（例如:<provider protocol=dubbo ..>）> @Spi注解上的默认值

具体加载和选择执行流程图

图片在线链接： https://www.processon.com/view/link/5fd4ae5c7d9c0806f72ee982

接下来我们从这一行代码分析，Dubbo如何动态的选择接口具体的实现

private static final Protocol REF_PROTOCOL = ExtensionLoader.getExtensionLoader(Protocol.class).getAdaptiveExtension();

1.ExtensionLoader.getExtensionLoader(Protocol.class)

这一部分的作用是dubbo从指定位置加载配置文件，读取到Protocol接口所有可配置的实现。最终的实现是new ExtensionLoader<T>(type)

if (type == null) {
    throw new IllegalArgumentException("Extension type == null");
}
if (!type.isInterface()) {
    throw new IllegalArgumentException("Extension type (" + type + ") is not an interface!");
}
if (!withExtensionAnnotation(type)) {
    throw new IllegalArgumentException("Extension type (" + type +
            ") is not an extension, because it is NOT annotated with @" + SPI.class.getSimpleName() + "!");
}


ExtensionLoader<T> loader = (ExtensionLoader<T>) EXTENSION_LOADERS.get(type);
if (loader == null) {
    EXTENSION_LOADERS.putIfAbsent(type, new ExtensionLoader<T>(type));
    loader = (ExtensionLoader<T>) EXTENSION_LOADERS.get(type);
}
return loader;

看一下ExtensionLoader的构造方法

private ExtensionLoader(Class<?> type) {
    this.type = type;
    objectFactory = (type == ExtensionFactory.class ? null : ExtensionLoader.getExtensionLoader(ExtensionFactory.class).getAdaptiveExtension());
}

因为我们这里的type是Protocol，所以这里objectFactory = ExtensionLoader.getExtensionLoader(ExtensionFactory.class).getAdaptiveExtension()

这里我们再拆成两部分来看

1.1ExtensionLoader.getExtensionLoader(ExtensionFactory.class)

这里的type是ExtensionFactory.class，所以就是简单的赋值type =ExtensionFactory.class, objectFactory = null

1.2 ExtensionLoader<ExtensionFactory>.getAdaptiveExtension()

这里基本上全是对缓存的处理，最终只有一行实现createAdaptiveExtension()

public T getAdaptiveExtension() {
    Object instance = cachedAdaptiveInstance.get();
    if (instance == null) {
        if (createAdaptiveInstanceError != null) {
            throw new IllegalStateException("Failed to create adaptive instance: " +
                    createAdaptiveInstanceError.toString(),
                    createAdaptiveInstanceError);
        }


        synchronized (cachedAdaptiveInstance) {
            instance = cachedAdaptiveInstance.get();
            if (instance == null) {
                try {
                    instance = createAdaptiveExtension();
                    cachedAdaptiveInstance.set(instance);
                } catch (Throwable t) {
                    createAdaptiveInstanceError = t;
                    throw new IllegalStateException("Failed to create adaptive instance: " + t.toString(), t);
                }
            }
        }
    }


    return (T) instance;
}

点进方法内部

private T createAdaptiveExtension() {
    try {
        return injectExtension((T) getAdaptiveExtensionClass().newInstance());
    } catch (Exception e) {
        throw new IllegalStateException("Can't create adaptive extension " + type + ", cause: " + e.getMessage(), e);
    }
}

从这里开始我们分成三个步骤来看

1.2.1getAdaptiveExtensionClass()

private Class<?> getAdaptiveExtensionClass() {
    getExtensionClasses();
    if (cachedAdaptiveClass != null) {
        return cachedAdaptiveClass;
    }
    return cachedAdaptiveClass = createAdaptiveExtensionClass();
}

先进入getExtensionClasses方法内部,穿过缓存处理，进入最终加载

private Map<String, Class<?>> loadExtensionClasses() {
    cacheDefaultExtensionName();


    Map<String, Class<?>> extensionClasses = new HashMap<>();
    loadDirectory(extensionClasses, DUBBO_INTERNAL_DIRECTORY, type.getName());
    loadDirectory(extensionClasses, DUBBO_INTERNAL_DIRECTORY, type.getName().replace("org.apache", "com.alibaba"));
    loadDirectory(extensionClasses, DUBBO_DIRECTORY, type.getName());
    loadDirectory(extensionClasses, DUBBO_DIRECTORY, type.getName().replace("org.apache", "com.alibaba"));
    loadDirectory(extensionClasses, SERVICES_DIRECTORY, type.getName());
    loadDirectory(extensionClasses, SERVICES_DIRECTORY, type.getName().replace("org.apache", "com.alibaba"));
    return extensionClasses;
}

第一行 cacheDefaultExtensionName 是将@Spi注解上的值作为默认实现的key缓存起来，最多只能指定一个默认实现。比如Protocol指定dubbo为默认实现,这里的type是ExtensionFactory，没有默认值

private void cacheDefaultExtensionName() {
    final SPI defaultAnnotation = type.getAnnotation(SPI.class);
    if (defaultAnnotation == null) {
        return;
    }


    String value = defaultAnnotation.value();
    if ((value = value.trim()).length() > 0) {
        String[] names = NAME_SEPARATOR.split(value);
        if (names.length > 1) {
            throw new IllegalStateException("More than 1 default extension name on extension " + type.getName()
                    + ": " + Arrays.toString(names));
        }
        if (names.length == 1) {
            cachedDefaultName = names[0];
        }
    }
}

接下来的6行是从指定目录位置加载接口的具体实现存储进Map里面，一共支持三个目录,因为dubbo捐献给Apache之后修改了目录，所以需要兼容迁移前后两种位置的接口名称,点进去看具体实现

private void loadDirectory(Map<String, Class<?>> extensionClasses, String dir, String type) {
    String fileName = dir + type;
    try {
        Enumeration<java.net.URL> urls;
        ClassLoader classLoader = findClassLoader();
        if (classLoader != null) {
            urls = classLoader.getResources(fileName);
        } else {
            urls = ClassLoader.getSystemResources(fileName);
        }
        if (urls != null) {
            while (urls.hasMoreElements()) {
                java.net.URL resourceURL = urls.nextElement();
                loadResource(extensionClasses, classLoader, resourceURL);
            }
        }
    } catch (Throwable t) {
        logger.error("Exception occurred when loading extension class (interface: " +
                type + ", description file: " + fileName + ").", t);
    }
}

从每一个jar包的对应位置去加载资源，配置文件中的等号左边是实现名称，右边是具体实现类的全限定名，以extensionFactory为例

adaptive=org.apache.dubbo.common.extension.factory.AdaptiveExtensionFactory
spi=org.apache.dubbo.common.extension.factory.SpiExtensionFactory
spring=org.apache.dubbo.config.spring.extension.SpringExtensionFactory

这里使用Class.forname来把具体实现类加载为Class对象

private void loadResource(Map<String, Class<?>> extensionClasses, ClassLoader classLoader, java.net.URL resourceURL) {
    try {
        try (BufferedReader reader = new BufferedReader(new InputStreamReader(resourceURL.openStream(), StandardCharsets.UTF_8))) {
            String line;
            while ((line = reader.readLine()) != null) {
                final int ci = line.indexOf('#');
                if (ci >= 0) {
                    line = line.substring(0, ci);
                }
                line = line.trim();
                if (line.length() > 0) {
                    try {
                        String name = null;
                        int i = line.indexOf('=');
                        if (i > 0) {
                            name = line.substring(0, i).trim();
                            line = line.substring(i + 1).trim();
                        }
                        if (line.length() > 0) {
                            loadClass(extensionClasses, resourceURL, Class.forName(line, true, classLoader), name);
                        }
                    } catch (Throwable t) {
                        IllegalStateException e = new IllegalStateException("Failed to load extension class (interface: " + type + ", class line: " + line + ") in " + resourceURL + ", cause: " + t.getMessage(), t);
                        exceptions.put(line, e);
                    }
                }
            }
        }
    } catch (Throwable t) {
        logger.error("Exception occurred when loading extension class (interface: " +
                type + ", class file: " + resourceURL + ") in " + resourceURL, t);
    }
}

加载进来的所有实现类被分成了三种：1.带@Adaptive注解被缓存起来（ cachedAdaptiveClass ）

2.构造方法带接口实例的，认为是接口的包装类，缓存在 cachedWrapperClasses中

3.其他的实例认为是可配置的实现，缓存在前面的map里面（ extensionClasses ）和 cachedActivates里面（带@Activate注解的）

private void loadClass(Map<String, Class<?>> extensionClasses, java.net.URL resourceURL, Class<?> clazz, String name) throws NoSuchMethodException {
    if (!type.isAssignableFrom(clazz)) {
        throw new IllegalStateException("Error occurred when loading extension class (interface: " +
                type + ", class line: " + clazz.getName() + "), class "
                + clazz.getName() + " is not subtype of interface.");
    }
    if (clazz.isAnnotationPresent(Adaptive.class)) {
        cacheAdaptiveClass(clazz);
    } else if (isWrapperClass(clazz)) {
        cacheWrapperClass(clazz);
    } else {
        clazz.getConstructor();
        if (StringUtils.isEmpty(name)) {
            name = findAnnotationName(clazz);
            if (name.length() == 0) {
                throw new IllegalStateException("No such extension name for the class " + clazz.getName() + " in the config " + resourceURL);
            }
        }


        String[] names = NAME_SEPARATOR.split(name);
        if (ArrayUtils.isNotEmpty(names)) {
            cacheActivateClass(clazz, names[0]);
            for (String n : names) {
                cacheName(clazz, n);
                saveInExtensionClass(extensionClasses, clazz, n);
            }
        }
    }
}

回到1.2.1 getAdaptiveExtensionClass方法

因为我们这里的type是ExtensionFactory，配置文件中存在@Adaptive的实现 AdaptiveExtensionFactory，所以这里我们使用了最高优先级的实现（存在缓存里面的AdaptiveExtensionFactory）直接返回了

注：Protocol文件里面没有@Adaptive的实现，所以会走下面的逻辑createAdaptiveExtensionClass,具体的实现放在标题2里面讲

1.2.2 Class.newInstance()

AdaptiveExtensionFactory类的实例化，去加载其他扩展实现存储在factories里面

public AdaptiveExtensionFactory() {
    ExtensionLoader<ExtensionFactory> loader = ExtensionLoader.getExtensionLoader(ExtensionFactory.class);
    List<ExtensionFactory> list = new ArrayList<ExtensionFactory>();
    for (String name : loader.getSupportedExtensions()) {
        list.add(loader.getExtension(name));
    }
    factories = Collections.unmodifiableList(list);
}

去除缓存处理，最终反射实例化对象

private T createExtension(String name) {
    Class<?> clazz = getExtensionClasses().get(name);
    if (clazz == null) {
        throw findException(name);
    }
    try {
        T instance = (T) EXTENSION_INSTANCES.get(clazz);
        if (instance == null) {
            EXTENSION_INSTANCES.putIfAbsent(clazz, clazz.newInstance());
            instance = (T) EXTENSION_INSTANCES.get(clazz);
        }
        injectExtension(instance);
        Set<Class<?>> wrapperClasses = cachedWrapperClasses;
        if (CollectionUtils.isNotEmpty(wrapperClasses)) {
            for (Class<?> wrapperClass : wrapperClasses) {
                instance = injectExtension((T) wrapperClass.getConstructor(type).newInstance(instance));
            }
        }
        return instance;
    } catch (Throwable t) {
        throw new IllegalStateException("Extension instance (name: " + name + ", class: " +
                type + ") couldn't be instantiated: " + t.getMessage(), t);
    }
}

1.2.3 InjectExtension()

因为这里是extensionFactory这里的objectFactory为Null，直接返回了，否则反射调用set方法注入到实体内部

private T injectExtension(T instance) {


    if (objectFactory == null) {
        return instance;
    }


    try {
        for (Method method : instance.getClass().getMethods()) {
            if (!isSetter(method)) {
                continue;
            }
            /**
             * Check {@link DisableInject} to see if we need auto injection for this property
             */
            if (method.getAnnotation(DisableInject.class) != null) {
                continue;
            }
            Class<?> pt = method.getParameterTypes()[0];
            if (ReflectUtils.isPrimitives(pt)) {
                continue;
            }


            try {
                String property = getSetterProperty(method);
                Object object = objectFactory.getExtension(pt, property);
                if (object != null) {
                    method.invoke(instance, object);
                }
            } catch (Exception e) {
                logger.error("Failed to inject via method " + method.getName()
                        + " of interface " + type.getName() + ": " + e.getMessage(), e);
            }


        }
    } catch (Exception e) {
        logger.error(e.getMessage(), e);
    }
    return instance;
}

2. ExtensionLoader.getAdaptiveExtension()

这里是ExtensionLoader<Protocol>的 getAdaptiveExtension方法，这里其他部分和1.2完全相同，只不过protocol没有@Adaptive的实现，所以这里会走 createAdaptiveExtensionClass方法的逻辑

private Class<?> createAdaptiveExtensionClass() {
    String code = new AdaptiveClassCodeGenerator(type, cachedDefaultName).generate();
    ClassLoader classLoader = findClassLoader();
    org.apache.dubbo.common.compiler.Compiler compiler = ExtensionLoader.getExtensionLoader(org.apache.dubbo.common.compiler.Compiler.class).getAdaptiveExtension();
    return compiler.compile(code, classLoader);
}

第一行是基于接口名称和缓存的默认实现名称来动态拼接一个java源文件出来，生成的代码如下：

可以看出来这是基于Protocol生成的动态代理实现，代理@Adaptive方法，

以refer方法为例，使用的扩展点名称 优先取参数url中的protocol，也就是我们写在配置中的protocol属性，最终会拼接在这个url上，如果没有则拿@Spi注解上的默认值 ，然后在缓存中通过扩展名拿到对应扩展实现类的class，反射创建扩展点实例，最终使用对应的扩展来完成对应的实现

package org.apache.dubbo.rpc;
import org.apache.dubbo.common.extension.ExtensionLoader;
public class Protocol$Adaptive implements org.apache.dubbo.rpc.Protocol {
    @Override
    public void destroy()  {
        throw new UnsupportedOperationException("The method public abstract void org.apache.dubbo.rpc.Protocol.destroy() of interface org.apache.dubbo.rpc.Protocol is not adaptive method!");
    }
    @Override
    public int getDefaultPort()  {
        throw new UnsupportedOperationException("The method public abstract int org.apache.dubbo.rpc.Protocol.getDefaultPort() of interface org.apache.dubbo.rpc.Protocol is not adaptive method!");
    }
    @Override
    public org.apache.dubbo.rpc.Invoker refer(java.lang.Class arg0, org.apache.dubbo.common.URL arg1) throws org.apache.dubbo.rpc.RpcException {
        if (arg1 == null) {
            throw new IllegalArgumentException("url == null");
        }
        org.apache.dubbo.common.URL url = arg1;
        String extName = ( url.getProtocol() == null ? "dubbo" : url.getProtocol() );
        if(extName == null){
            throw new IllegalStateException("Failed to get extension (org.apache.dubbo.rpc.Protocol) name from url (" + url.toString() + ") use keys([protocol])");
        }
        org.apache.dubbo.rpc.Protocol extension = (org.apache.dubbo.rpc.Protocol)ExtensionLoader.getExtensionLoader(org.apache.dubbo.rpc.Protocol.class).getExtension(extName);
        return extension.refer(arg0, arg1);
    }
    @Override
    public org.apache.dubbo.rpc.Exporter export(org.apache.dubbo.rpc.Invoker arg0) throws org.apache.dubbo.rpc.RpcException {
        if (arg0 == null){
            throw new IllegalArgumentException("org.apache.dubbo.rpc.Invoker argument == null");
        }
        if (arg0.getUrl() == null){
            throw new IllegalArgumentException("org.apache.dubbo.rpc.Invoker argument getUrl() == null");
        }
        org.apache.dubbo.common.URL url = arg0.getUrl();
        String extName = ( url.getProtocol() == null ? "dubbo" : url.getProtocol() );
        if(extName == null){
            throw new IllegalStateException("Failed to get extension (org.apache.dubbo.rpc.Protocol) name from url (" + url.toString() + ") use keys([protocol])");
        }
        org.apache.dubbo.rpc.Protocol extension = (org.apache.dubbo.rpc.Protocol)ExtensionLoader.getExtensionLoader(org.apache.dubbo.rpc.Protocol.class).getExtension(extName);
        return extension.export(arg0);
    }
}

后面的代码则是使用Compile来将生成的代码编译成Class对象，这里就不详细介绍了

胡晗-

关注

0
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
2.Dubbo动态扩展

我们知道dubbo通过SPI机制实现了灵活的动态扩展，但是这些扩展的优先级怎么样？怎么去判断最后采用的是哪个实现？先上结论：@Adaptive注解实现类 >配置名对应的实现（例如:<provider protocol=dubbo ..>）> @Spi注解上的默认值具体加载和选择执行流程图图片在线链接：https://www.processon.com/view/link/5fd4ae5c7d9c0806f72ee982接下来我们从这一行代码分析，Du...
复制链接

扫一扫

专栏目录