[jdt-dev] Performance issues using IType interface

[Slava Kabanovich <vkabanovich@xxxxxxxxxx>]

Hello,

I work on Batch and CDI models for JBossTools in Eclipse. Incremental 
builders for the models look for types that either implement some 
interfaces (Batch), or have bean defining annotations (CDI). At present 
this is implemented with requests to IType interface. In a large 
workspace, with a lot of jars in classpath, at first build (or at a 
change in class path) jar entries have to be checked for being Batch or 
CDI archive, there is no simple way to do that (in CDI since 1.1, CDI 
1.0 had required beans.xml that made life much easier) other than 
checking all types in jar. Tests show that in average about 2000 IType 
objects may be checked in one second, which results in unacceptably long 
build time for large workspaces. Batch and CDI build take 2 to 3 times 
longer than Java build. It makes one to assume that Java build uses 
internally more efficient model than org.eclipse.jdt.core.

Could it be possible to get faster methods for checking inheritance and 
annotations? It may be still ok to work with IType interface for objects 
verified as Batch artifacts or CDI beans/annotations, but it is of great 
importance to be able to quickly rule out irrelevant types. Could you 
please advise me already existing ways to solve this problem, or 
consider implementing in JDT new high performance requests?

Thank you.

Best regards,
Viacheslav Kabanovich