Bug 66442 - Ambigous Error Message Issuance - no match for this type name: MessageCommunicator [Xlint:invalidAbsoluteTypeName]
Summary: Ambigous Error Message Issuance - no match for this type name: MessageCommuni...
Status: NEW
Alias: None
Product: AspectJ
Classification: Tools
Component: Compiler (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 2000
: P5 normal (vote)
Target Milestone: ---   Edit
Assignee: Adrian Colyer CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-09 19:09 EDT by Michael McConnell CLA
Modified: 2007-10-23 06:02 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael McConnell CLA 2004-06-09 19:09:33 EDT
1. Misspelled type name: In this case, the type won't exist
    anywhere in the system. This also includes case of fully
    specified type name with missed/misspelled packages.
 2. Correctly spelled type name but missed package statement
    (and type not in the same package as the aspect): In
    essense the type isn't visible to the aspect.
 3. Type name specified as wildcarded package: This would be
    case when pointcut say something like call(com..MyTypeName.*(..)).
    In this case, you don't even need a package statement and
    the program will still compile fine.
    (This situation is actually covered by a different XLint
     warning, which is turned off by default).

why does an absolute type name needs an import when a wildcarded type name does 
not?

If the lack of a wildcard combined with the lack of an import makes a type 
invisible to an aspect, why is this not an error? When is this correct?