Take for example these two abbreviated files (they are found in the
xml/schema/schemaui module on release55 branch of NB CVS, for the sake of
reproducing the problem):

CategorizedChildren.java:

    public CategorizedChildren(SchemaUIContext context, 
            SchemaComponentReference<C> reference) {
        this(context,reference,null);
    }

    public CategorizedChildren(SchemaUIContext context, 
            SchemaComponentReference<C> reference, 
            List<Class<? extends SchemaComponent>> childFilters) {
        ....
    }

CategorizedSchemaNodeFactory.java:

    public <C extends SchemaComponent> Children createChildren(
            Node parent, SchemaComponentReference<C> reference) {
        return new CategorizedChildren<C>(getContext(), reference,
                getChildFilters());
    }

Say I invoke Find Usages on the second constructor of CategorizedChildren (the
one with three parameters). The results include only the other constructor, and
do not include the usage in CategorizedSchemaNodeFactory.

Now say I remove the "<C>" from CategorizedSchemaNodeFactory and re-run the Find
Usages -- this time it finds the usage in CategorizedSchemaNodeFactory.

It seems to me that this is a bug, the <C> in CSNF should not matter one way or
the other, it is a valid usage of the constructor in any case.