IJvmModelInferrer.NullImpl (org.eclipse.xtext.xbase 2.30.0.RC2 API)

java.lang.Object
- org.eclipse.xtext.xbase.jvmmodel.IJvmModelInferrer.NullImpl

All Implemented Interfaces:: IJvmModelInferrer

Enclosing interface:: IJvmModelInferrer

public static class IJvmModelInferrer.NullImpl
extends java.lang.Object
implements IJvmModelInferrer

A null-implementation.

Nested Class Summary
- Nested classes/interfaces inherited from interface org.eclipse.xtext.xbase.jvmmodel.IJvmModelInferrer
  IJvmModelInferrer.NullImpl

Constructor Summary

Constructors
Constructor Description

NullImpl()

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method	Description
`void`	`infer(org.eclipse.emf.ecore.EObject e, IJvmDeclaredTypeAcceptor acceptor, boolean preIndexingPhase)`	This method is called at two different times in a resource's life-cycle, reflected by whether {preIndexingPhase} is set to `true` or `false`.

Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

- Constructor Detail
  - NullImpl
```
public NullImpl()
```
- Method Detail
  - infer
```
public void infer(org.eclipse.emf.ecore.EObject e,
                  IJvmDeclaredTypeAcceptor acceptor,
                  boolean preIndexingPhase)
```
    Description copied from interface: IJvmModelInferrer
    
    This method is called at two different times in a resource's life-cycle, reflected by whether {preIndexingPhase} is set to true or false. When set to true everything is still in a pre-indexing phase, that means linking hasn't been done yet. In this phase you just need to create the Jvm-elements which should be indexed (i.e. found globally). For regular Xbase expressions only the JvmTypes with the correct qualified name are needed at this point.
    
    You must only infer Jvm elements which directly result from elements contained in the current resource!
    
    When this method is called with preIndexingPhase set to false, you need to do the full inference including setting all links. But still you have to it in a particular order. First you need to create the complete tree structure and make sure you have passed the created JvmTypes to the acceptor. Only pass top level JvmTypes to the acceptor. Only if the tree structure is created and its root types have been passed to the acceptor, you are free to resolve any cross references.

Specified by:: infer in interface IJvmModelInferrer
Parameters:: e - the root element from the parse result; acceptor - an acceptor awaiting derived root JvmDeclaredTypes; preIndexingPhase - whether the call is done in before indexing. During this phase clients may not rely on any global indexing information and only need to provide the information needed by the language's IDefaultResourceDescriptionStrategy. IF not implemented differently this is just the JvmDeclaredTypes with their qualified name, but no members and no other data.