[aspectj-users] Re: [NEWSDELIVER] Re: A question about reflection and we

[Matthew Webster <matthew_webster@xxxxxxxxxx>]

James,

This problem is related to https://bugs.eclipse.org/bugs/show_bug.cgi?id=116229.
The existing PointcutParser interface implicitly creates a World and does
not allow any configuration including classpath or lint. I think the user
should create and configure a World _first_ then create the parser from
that. Please raise a bug. In the meantime to work around the problem enure
you define and compile the types with your testcase you refer to e.g. create
a "main" class.

Cheers

Matthew Webster
AOSD Project
Java Technology Centre, MP146
IBM Hursley Park, Winchester,  SO21 2JN, England
Telephone: +44 196 2816139 (external) 246139 (internal) 
Email: Matthew Webster/UK/IBM @ IBMGB, matthew_webster@xxxxxxxxxx
http://w3.hursley.ibm.com/~websterm/

To:        undisclosed-recipients:;
cc:        
Subject:        [NEWSDELIVER] Re: A question about reflection and weaver tools APIs



James Gan wrote:
> Hi, all
>
> I'm testing the reflection and weaver tools APIs. When I using following
> code:
>
> PointcutParser parse = new PointcutParser();
> String expr = "call(public * main.hello(..)";
> PointcutExpression pex = parse.parsePointcutExpression(expr);
>
> Whenever I use a full qualified class name in pointcut _expression_, an
> exception is throwed out:
> java.lang.IllegalArgumentException: warning no match for this type name:
> obj [Xlint:invalidAbsoluteTypeName]
>
> I try to turn off this Lint exception. But it seems I must access to
> world field of PointcutParser. This is inconvenient because world field
> is not exposed by PointcutParser. Could you please tell me how can I
> turn off this boring exception?
>
> Thanks a lot!
> James Gan

I suspect this is an oversight in the API - please raise an AspectJ bug
for us to look into it.

Andy.

(ps. you will get even faster responses if you can use the mailing list
rather than the newsgroup...)