This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 174511 - [68cat] Improve scanning (SoD per project)
Summary: [68cat] Improve scanning (SoD per project)
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P3 blocker (vote)
Assignee: issues@performance
Depends on:
Reported: 2009-10-14 09:10 UTC by Peter Nabbefeld
Modified: 2009-10-19 14:31 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Peter Nabbefeld 2009-10-14 09:10:40 UTC
[ JDK VERSION : 1.6.* ]

Please add an abstract class to be registered in a project's lookup,
so a project type (BTW, want to create my own) can decide whether to
scan a jar file or classpath.

public abstract class ProjectIndexingActivityInterceptor {
    public final IndexingActivityInterceptor
getGlobalIndexingActivityInterceptor() {

    public final refreshJarOrFolder(FileObject path) {

    public abstract shouldScan(FileObject path);

Comment 1 Peter Nabbefeld 2009-10-14 09:27:55 UTC
public abstract boolean shouldScan(FileObject path);
Comment 2 Filip Zamboj 2009-10-19 13:29:28 UTC
not sure if this belongs to performance. thanks. 
Comment 3 Peter Nabbefeld 2009-10-19 14:13:57 UTC
My problem is just, I'm working on sources for a non-J2EE server. Thus, NB does not know, when sources are updated and
checks the modification status without necessity :(

If I'd implement my own project type and/or actions, I could tell NB when to do scanning - and when not. This is
especially important, as the sources are on a mapped device (Windows) :(

It would thus help to improve performance significantly, if it would be possible to control scanning.