Dubbo源码学习--SPI实现@SPI和@Adaptive

迈不过友情╰ 2022-06-09 01:06 347阅读 0赞

上一篇博客 Dubbo入门学习—Dubbo服务提供接口SPI机制我们已经简单介绍了Dubbo的SPI机制,这篇博客我们来剖析一下Dubbo是如何使用SPI机制的,在接口中使用@SPI(“值”)使用默认的实现类,如果我们不想使用默认的实现类是如何处理的。

1、获取指定实现类

在ExtensionLoader中获取默认实现类或者通过实现类名称来获取实现类。

  1. Protocol refprotocol = ExtensionLoader.getExtensionLoader(Protocol.class).getDefaultExtension();
  2. Protocol refprotocol = ExtensionLoader.getExtensionLoader(Protocol.class).getExtension("dubbo");

这样获取的都是实现类DubboProtocol,在之前一篇博客中我们已经了解到,实现类的对应关系是配置在文件中的,从ExtensionLoader会解析文件将数据添加到一个Map中,这样可以直接通过“dubbo”来获取到实现类DubboProtocol。这种实现还是比较简单,但有一个问题就是需要在代码中写死使用哪个实现类,这个就和SPI的初衷有所差别了,因此Dubbo提供了一个另外一个注解@@Adaptive。
2、获取适配器类

Dubbo通过注解@Adaptive作为标记实现了一个适配器类,并且这个类是动态生成的,因此在Dubbo的源码中是看不到代码的,但是我们还是可以看到其实现方式的。Dubbo提供一个动态的适配器类的原因就是可以通过配置文件来动态的使用想要的接口实现类,并且不用改变任何接口的代码,简单来说其也是通过代理来实现的。

  1. @SPI("dubbo")
  2. public interface Protocol {
  3. int getDefaultPort();
  4. @Adaptive
  5. <T> Exporter<T> export(Invoker<T> invoker) throws RpcException;
  6. @Adaptive
  7. <T> Invoker<T> refer(Class<T> type, URL url) throws RpcException;
  8. void destroy();
  9. }

在接口Protocol的两个方法export和refer方法中都添加了注解@Adaptive,我们可以认为这两个接口方法会被代理实现。

ExtensionLoader提供了接口获取代理类的方法:

  1. Protocol refprotocol = ExtensionLoader.getExtensionLoader(Protocol.class).getAdaptiveExtension();

1、getAdaptiveExtension首先尝试从缓存中获取实例,如果不存在则创建一个新的实例

  1. @SuppressWarnings("unchecked")
  2. public T getAdaptiveExtension() {
  3. Object instance = cachedAdaptiveInstance.get();
  4. if (instance == null) {
  5. if(createAdaptiveInstanceError == null) {
  6. synchronized (cachedAdaptiveInstance) {
  7. instance = cachedAdaptiveInstance.get();
  8. if (instance == null) {
  9. try {
  10. //创建代理类
  11. instance = createAdaptiveExtension();
  12. cachedAdaptiveInstance.set(instance);
  13. } catch (Throwable t) {
  14. createAdaptiveInstanceError = t;
  15. throw new IllegalStateException("fail to create adaptive instance: " + t.toString(), t);
  16. }
  17. }
  18. }
  19. }
  20. else {
  21. throw new IllegalStateException("fail to create adaptive instance: " + createAdaptiveInstanceError.toString(), createAdaptiveInstanceError);
  22. }
  23. }
  24. return (T) instance;
  25. }

2、createAdaptiveExtension获取一个对象在初始化

  1. @SuppressWarnings("unchecked")
  2. private T createAdaptiveExtension() {
  3. try {
  4. return injectExtension((T) getAdaptiveExtensionClass().newInstance());
  5. } catch (Exception e) {
  6. throw new IllegalStateException("Can not create adaptive extenstion " + type + ", cause: " + e.getMessage(), e);
  7. }
  8. }

3、getAdaptiveExtensionClass获取类对象

  1. private Class<?> getAdaptiveExtensionClass() {
  2. getExtensionClasses();
  3. if (cachedAdaptiveClass != null) {
  4. return cachedAdaptiveClass;
  5. }
  6. return cachedAdaptiveClass = createAdaptiveExtensionClass();
  7. }

4、createAdaptiveExtensionClass中首先会获取代理类的源码,然后在编译源码获取一个Class

  1. private Class<?> createAdaptiveExtensionClass() {
  2. //获取一个字符串源码
  3. String code = createAdaptiveExtensionClassCode();
  4. ClassLoader classLoader = findClassLoader();
  5. com.alibaba.dubbo.common.compiler.Compiler compiler = ExtensionLoader.getExtensionLoader(com.alibaba.dubbo.common.compiler.Compiler.class).getAdaptiveExtension();
  6. //编译生成代理类
  7. return compiler.compile(code, classLoader);
  8. }

5、Dubbo实现一个适配器类的关键在createAdaptiveExtensionClassCode,会生成一个类的代理适配器类的源码

  1. //生成一个类的代理类源码
  2. private String createAdaptiveExtensionClassCode() {
  3. StringBuilder codeBuidler = new StringBuilder();
  4. Method[] methods = type.getMethods();
  5. boolean hasAdaptiveAnnotation = false;
  6. for(Method m : methods) {
  7. if(m.isAnnotationPresent(Adaptive.class)) {
  8. hasAdaptiveAnnotation = true;
  9. break;
  10. }
  11. }
  12. // 完全没有Adaptive方法,则不需要生成Adaptive类
  13. if(! hasAdaptiveAnnotation)
  14. throw new IllegalStateException("No adaptive method on extension " + type.getName() + ", refuse to create the adaptive class!");
  15. codeBuidler.append("package " + type.getPackage().getName() + ";");
  16. codeBuidler.append("\nimport " + ExtensionLoader.class.getName() + ";");
  17. codeBuidler.append("\npublic class " + type.getSimpleName() + "$Adpative" + " implements " + type.getCanonicalName() + " {");
  18. for (Method method : methods) {
  19. Class<?> rt = method.getReturnType();
  20. Class<?>[] pts = method.getParameterTypes();
  21. Class<?>[] ets = method.getExceptionTypes();
  22. Adaptive adaptiveAnnotation = method.getAnnotation(Adaptive.class);
  23. StringBuilder code = new StringBuilder(512);
  24. if (adaptiveAnnotation == null) {
  25. code.append("throw new UnsupportedOperationException(\"method ")
  26. .append(method.toString()).append(" of interface ")
  27. .append(type.getName()).append(" is not adaptive method!\");");
  28. } else {
  29. int urlTypeIndex = -1;
  30. for (int i = 0; i < pts.length; ++i) {
  31. if (pts[i].equals(URL.class)) {
  32. urlTypeIndex = i;
  33. break;
  34. }
  35. }
  36. // 有类型为URL的参数
  37. if (urlTypeIndex != -1) {
  38. // Null Point check
  39. String s = String.format("\nif (arg%d == null) throw new IllegalArgumentException(\"url == null\");",
  40. urlTypeIndex);
  41. code.append(s);
  42. s = String.format("\n%s url = arg%d;", URL.class.getName(), urlTypeIndex);
  43. code.append(s);
  44. }
  45. // 参数没有URL类型
  46. else {
  47. String attribMethod = null;
  48. // 找到参数的URL属性
  49. LBL_PTS:
  50. for (int i = 0; i < pts.length; ++i) {
  51. Method[] ms = pts[i].getMethods();
  52. for (Method m : ms) {
  53. String name = m.getName();
  54. if ((name.startsWith("get") || name.length() > 3)
  55. && Modifier.isPublic(m.getModifiers())
  56. && !Modifier.isStatic(m.getModifiers())
  57. && m.getParameterTypes().length == 0
  58. && m.getReturnType() == URL.class) {
  59. urlTypeIndex = i;
  60. attribMethod = name;
  61. break LBL_PTS;
  62. }
  63. }
  64. }
  65. if(attribMethod == null) {
  66. throw new IllegalStateException("fail to create adative class for interface " + type.getName()
  67. + ": not found url parameter or url attribute in parameters of method " + method.getName());
  68. }
  69. // Null point check
  70. String s = String.format("\nif (arg%d == null) throw new IllegalArgumentException(\"%s argument == null\");",
  71. urlTypeIndex, pts[urlTypeIndex].getName());
  72. code.append(s);
  73. s = String.format("\nif (arg%d.%s() == null) throw new IllegalArgumentException(\"%s argument %s() == null\");",
  74. urlTypeIndex, attribMethod, pts[urlTypeIndex].getName(), attribMethod);
  75. code.append(s);
  76. s = String.format("%s url = arg%d.%s();",URL.class.getName(), urlTypeIndex, attribMethod);
  77. code.append(s);
  78. }
  79. String[] value = adaptiveAnnotation.value();
  80. // 没有设置Key,则使用“扩展点接口名的点分隔 作为Key
  81. if(value.length == 0) {
  82. char[] charArray = type.getSimpleName().toCharArray();
  83. StringBuilder sb = new StringBuilder(128);
  84. for (int i = 0; i < charArray.length; i++) {
  85. if(Character.isUpperCase(charArray[i])) {
  86. if(i != 0) {
  87. sb.append(".");
  88. }
  89. sb.append(Character.toLowerCase(charArray[i]));
  90. }
  91. else {
  92. sb.append(charArray[i]);
  93. }
  94. }
  95. value = new String[] {sb.toString()};
  96. }
  97. boolean hasInvocation = false;
  98. for (int i = 0; i < pts.length; ++i) {
  99. if (pts[i].getName().equals("com.alibaba.dubbo.rpc.Invocation")) {
  100. // Null Point check
  101. String s = String.format("\nif (arg%d == null) throw new IllegalArgumentException(\"invocation == null\");", i);
  102. code.append(s);
  103. s = String.format("\nString methodName = arg%d.getMethodName();", i);
  104. code.append(s);
  105. hasInvocation = true;
  106. break;
  107. }
  108. }
  109. String defaultExtName = cachedDefaultName;
  110. String getNameCode = null;
  111. for (int i = value.length - 1; i >= 0; --i) {
  112. if(i == value.length - 1) {
  113. if(null != defaultExtName) {
  114. if(!"protocol".equals(value[i]))
  115. if (hasInvocation)
  116. getNameCode = String.format("url.getMethodParameter(methodName, \"%s\", \"%s\")", value[i], defaultExtName);
  117. else
  118. getNameCode = String.format("url.getParameter(\"%s\", \"%s\")", value[i], defaultExtName);
  119. else
  120. getNameCode = String.format("( url.getProtocol() == null ? \"%s\" : url.getProtocol() )", defaultExtName);
  121. }
  122. else {
  123. if(!"protocol".equals(value[i]))
  124. if (hasInvocation)
  125. getNameCode = String.format("url.getMethodParameter(methodName, \"%s\", \"%s\")", value[i], defaultExtName);
  126. else
  127. getNameCode = String.format("url.getParameter(\"%s\")", value[i]);
  128. else
  129. getNameCode = "url.getProtocol()";
  130. }
  131. }
  132. else {
  133. if(!"protocol".equals(value[i]))
  134. if (hasInvocation)
  135. getNameCode = String.format("url.getMethodParameter(methodName, \"%s\", \"%s\")", value[i], defaultExtName);
  136. else
  137. getNameCode = String.format("url.getParameter(\"%s\", %s)", value[i], getNameCode);
  138. else
  139. getNameCode = String.format("url.getProtocol() == null ? (%s) : url.getProtocol()", getNameCode);
  140. }
  141. }
  142. code.append("\nString extName = ").append(getNameCode).append(";");
  143. // check extName == null?
  144. String s = String.format("\nif(extName == null) " +
  145. "throw new IllegalStateException(\"Fail to get extension(%s) name from url(\" + url.toString() + \") use keys(%s)\");",
  146. type.getName(), Arrays.toString(value));
  147. code.append(s);
  148. s = String.format("\n%s extension = (%<s)%s.getExtensionLoader(%s.class).getExtension(extName);",
  149. type.getName(), ExtensionLoader.class.getSimpleName(), type.getName());
  150. code.append(s);
  151. // return statement
  152. if (!rt.equals(void.class)) {
  153. code.append("\nreturn ");
  154. }
  155. s = String.format("extension.%s(", method.getName());
  156. code.append(s);
  157. for (int i = 0; i < pts.length; i++) {
  158. if (i != 0)
  159. code.append(", ");
  160. code.append("arg").append(i);
  161. }
  162. code.append(");");
  163. }
  164. codeBuidler.append("\npublic " + rt.getCanonicalName() + " " + method.getName() + "(");
  165. for (int i = 0; i < pts.length; i ++) {
  166. if (i > 0) {
  167. codeBuidler.append(", ");
  168. }
  169. codeBuidler.append(pts[i].getCanonicalName());
  170. codeBuidler.append(" ");
  171. codeBuidler.append("arg" + i);
  172. }
  173. codeBuidler.append(")");
  174. if (ets.length > 0) {
  175. codeBuidler.append(" throws ");
  176. for (int i = 0; i < ets.length; i ++) {
  177. if (i > 0) {
  178. codeBuidler.append(", ");
  179. }
  180. codeBuidler.append(ets[i].getCanonicalName());
  181. }
  182. }
  183. codeBuidler.append(" {");
  184. codeBuidler.append(code.toString());
  185. codeBuidler.append("\n}");
  186. }
  187. codeBuidler.append("\n}");
  188. if (logger.isDebugEnabled()) {
  189. logger.debug(codeBuidler.toString());
  190. }
  191. return codeBuidler.toString();
  192. }

Protocol refprotocol = ExtensionLoader.getExtensionLoader(Protocol.class).getAdaptiveExtension(); 生成的代理适配器类的源码如下:

  1. package com.alibaba.dubbo.rpc;
  2. import com.alibaba.dubbo.common.extension.ExtensionLoader;
  3. public class Protocol$Adpative implements com.alibaba.dubbo.rpc.Protocol {
  4. public void destroy() {
  5. throw new UnsupportedOperationException("method public abstract void com.alibaba.dubbo.rpc.Protocol.destroy() of interface com.alibaba.dubbo.rpc.Protocol is not adaptive method!");
  6. }
  7. public int getDefaultPort() {
  8. throw new UnsupportedOperationException("method public abstract int com.alibaba.dubbo.rpc.Protocol.getDefaultPort() of interface com.alibaba.dubbo.rpc.Protocol is not adaptive method!");
  9. }
  10. public com.alibaba.dubbo.rpc.Exporter (com.alibaba.dubbo.rpc.Invoker arg0) throws com.alibaba.dubbo.rpc.RpcException {
  11. if (arg0 == null) throw new IllegalArgumentException("com.alibaba.dubbo.rpc.Invoker argument == null");
  12. if (arg0.getUrl() == null) throw new IllegalArgumentException("com.alibaba.dubbo.rpc.Invoker argument getUrl() == null");com.alibaba.dubbo.common.URL url = arg0.getUrl();
  13. String extName = ( url.getProtocol() == null ? "dubbo" : url.getProtocol() );
  14. if(extName == null) throw new IllegalStateException("Fail to get extension(com.alibaba.dubbo.rpc.Protocol) name from url(" + url.toString() + ") use keys([protocol])");
  15. com.alibaba.dubbo.rpc.Protocol extension = (com.alibaba.dubbo.rpc.Protocol)ExtensionLoader.getExtensionLoader(com.alibaba.dubbo.rpc.Protocol.class).getExtension(extName);
  16. return extension.export(arg0);
  17. }
  18. public com.alibaba.dubbo.rpc.Invoker refer(java.lang.Class arg0, com.alibaba.dubbo.common.URL arg1) throws com.alibaba.dubbo.rpc.RpcException {
  19. if (arg1 == null) throw new IllegalArgumentException("url == null");
  20. com.alibaba.dubbo.common.URL url = arg1;
  21. String extName = ( url.getProtocol() == null ? "dubbo" : url.getProtocol() );
  22. if(extName == null) throw new IllegalStateException("Fail to get extension(com.alibaba.dubbo.rpc.Protocol) name from url(" + url.toString() + ") use keys([protocol])");
  23. com.alibaba.dubbo.rpc.Protocol extension = (com.alibaba.dubbo.rpc.Protocol)ExtensionLoader.getExtensionLoader(com.alibaba.dubbo.rpc.Protocol.class).getExtension(extName);
  24. return extension.refer(arg0, arg1);
  25. }
  26. }

我们分析一下,生成的代理器类如果被调用refer方法时会发生的处理操作,简单来说是通过代理方式来生成一个适配器类。

  1. public com.alibaba.dubbo.rpc.Invoker refer(java.lang.Class arg0, com.alibaba.dubbo.common.URL arg1) throws com.alibaba.dubbo.rpc.RpcException {
  2. if (arg1 == null) throw new IllegalArgumentException("url == null");
  3. //被Adattive注解的方法中有个参数必须是URL对象或者参数可以通过getUrl()获取到一个url不然会抛出异常
  4. com.alibaba.dubbo.common.URL url = arg1;
  5. //首先会判断url中是否指定了协议,不然使用默认
  6. String extName = ( url.getProtocol() == null ? "dubbo" : url.getProtocol() );
  7. if(extName == null) throw new IllegalStateException("Fail to get extension(com.alibaba.dubbo.rpc.Protocol) name from url(" + url.toString() + ") use keys([protocol])");
  8. //获取实现类
  9. com.alibaba.dubbo.rpc.Protocol extension = (com.alibaba.dubbo.rpc.Protocol)ExtensionLoader.getExtensionLoader(com.alibaba.dubbo.rpc.Protocol.class).getExtension(extName);
  10. //最终调用实现类的refer方法
  11. return extension.refer(arg0, arg1);
  12. }

总结:Dubbo通过两个注解SPI和Adaptive,通过参数中URL.getProtocol可以动态的使用各种实现类。

发表评论

表情:
评论列表 (有 0 条评论,347人围观)

还没有评论,来说两句吧...

相关阅读

    相关 dubbo解析-spi(五)

    Dubbo源码解析系列文章均来自肥朝简书 前言 之前对dubbo的`SPI`进行了四篇的分享.大家对这个概念有了一些初步的了解.谈到编程水平如何进阶,大家可能都会异口同