今天在用JDT的DOM API分析Java源代码时遇到如下问题:
当用户在JDT Editor里面编辑代码时,如果需要JDT进行参数推荐,则会触发我们自己的代码。而此时,不知何故,我们的ASTVisitor的代码中无法resolve一个TypeDeclaration。即调用TypeDeclaration.resolveBinding()的返回值为null。进而导致一个NPE。
后来老杨等人找到这么一段API文档(是ASTParser.setResolveBindings()的):
...
When source is supplied by setSource(char[]), the location must be established explicitly by setting an environment using setProject(IJavaProject) or setEnvironment(String[], String[], String[], boolean) and a unit name setUnitName(String). Note that the compiler options that affect doc comment checking may also affect whether any bindings are resolved for nodes within doc comments.
...
然后根据此文档的指示,老杨等人使用了如下代码,就解决了:
特此记录一下 :arrow:
当用户在JDT Editor里面编辑代码时,如果需要JDT进行参数推荐,则会触发我们自己的代码。而此时,不知何故,我们的ASTVisitor的代码中无法resolve一个TypeDeclaration。即调用TypeDeclaration.resolveBinding()的返回值为null。进而导致一个NPE。
后来老杨等人找到这么一段API文档(是ASTParser.setResolveBindings()的):
...
When source is supplied by setSource(char[]), the location must be established explicitly by setting an environment using setProject(IJavaProject) or setEnvironment(String[], String[], String[], boolean) and a unit name setUnitName(String). Note that the compiler options that affect doc comment checking may also affect whether any bindings are resolved for nodes within doc comments.
...
然后根据此文档的指示,老杨等人使用了如下代码,就解决了:
ASTParser parser = ASTParser.newParser(AST.JLS3);
parser.setSource(srcString.toCharArray());
parser.setProject(icu.getJavaProject());
IPath path = icu.getPath();
parser.setUnitName(path.toString());
parser.setResolveBindings(true);
parser.setStatementsRecovery(true);
completeCU = (CompilationUnit) parser.createAST(null);
特此记录一下 :arrow: