ASTParser.createAST fails at handling missing types

[mickaelistria]

While working on DOM based operation ( #1863 ), I noticed that a DOM created with ASTParser.createAST is not always complete and can fail at resolving some bindings.

Inspired from ASTConverterTest15.test0238_2

	public void test0238_2() throws JavaModelException, CoreException {
		this.workingCopy = getWorkingCopy("/Converter15/src/test0238/X.java",
			"""
			package test0238;
			public class X extends A {
			}
			""", true /*resolve*/);
		ASTParser parser = ASTParser.newParser(AST.getJLSLatest());
		parser.setBindingsRecovery(true);
		parser.setResolveBindings(true);
		parser.setStatementsRecovery(true);
		parser.setSource(this.workingCopy);
		parser.setProject((IJavaProject)ResourcesPlugin.getWorkspace().getRoot().getProject("Converter15").getNature(JavaCore.NATURE_ID));
		CompilationUnit unit = (CompilationUnit)  parser.createAST(null);
		TypeDeclaration typeDeclaration = (TypeDeclaration) unit.types().get(0);
		ITypeBinding superTypeBinding = typeDeclaration.resolveBinding().getSuperclass();
		IMethodBinding[] methodBindings = superTypeBinding.getDeclaredMethods();
		assertEquals("wrong size", 2, methodBindings.length);
	}

fails because the method referencing the unresolved type isn't included.

The expectation here would be that this piece of code returns a CompilationUnit DOM and bindings fully equivalent to what CompilationUnit.buildStructure() would process with the same settings (recovery).

CompilationUnit.buildStructure uses a combination of parse/resolve which is similar to what createAST does, however, it looks like createAST doesn't properly set the resolution context/environment before computing the bindings.

[mickaelistria]

The "leaf" problem seems to be that environment.problemReporter.referenceContext is null invoking TypeBinding.resolveMethods() when the compilation unit is built using ASTParser.createAST