|Re: Incremental mode [message #1044051 is a reply to message #1043813]
||Thu, 18 April 2013 12:41
| Fabien Giquel
Registered: July 2009
I had a look at the JDTVisitor. Its seems to me that the code is complete for what it was supposed to do :
- the visit(VariableDeclarationFragment) does the job to determine previously references and reuse the proxy (call setProxy(false)).
- the visit(FieldDeclaration) does not have to do it, since a FieldDeclaration is just a container for VariableDeclarationFragment. No other statement has reference to one "FieldDeclaration".
Now may be the problem is that you consider the existing parameter called "INCREMENTAL_MODE" as a way to manage the incremental update of one java model. Actually the INCREMENTAL_MODE just proposes some memory optimization, not an attempt of "incremental model update" as you want to do. The memory optimization works as follows :
- when the jdtvisitor encouters some reference to unknown java type/method/field, a "proxy" element is created
- if INCREMENTAL_MODE==false, the discoverer tries to substitute "proxies" with concrete elements at the final end of discovery
- if INCREMENTAL_MODE==true, the discoverer tries to substitute "proxies" with concrete elements at many steps (each java package, and each time a type/method/field declaration is visited)
You may ask through one bugzilla entry to set some fields from JdtVisitor/JavaReader "protected". When possible, one commiter will study the impacts of this modification.
hoping it will help you,
Powered by FUDForum
. Page generated in 0.02552 seconds