|
|
Re: Problem with AspectJ syntax: "no match for this type name" [message #41875 is a reply to message #41843] |
Mon, 04 October 2004 12:42 |
Eclipse User |
|
|
|
Originally posted by: mchapman.uk.ibm.com
Hi Michael,
If you match against "Hello*.*" then you don't get a warning, but
if you do "Hello.*" you get the "no match for this type name"
warning, if the aspect cannot resolve the "Hello" type. So wildcards
are treated differently to absolute type names. In this case you
would need to tell the compiler which Hello you are referring so,
with something like "import foo.Hello;"
That doesn't however seem to completely explain the problem you are
seeing. The compiler is telling you it cannot resolve the
package3.SpecificClassNameHere class, despite it being qualified with
the package name. Could there perhaps be something unusual with your
project setup or layout? What happens if you refer to that class
from elsewhere in the aspect (from advice or a method)?
Regards,
Matt.
On Mon, 04 Oct 2004 12:41:12 +0200, Michael Moser wrote:
> BTW: I just noticed, that adding a "*" makes the problem go away:
>
> i.e. if I instead of
> -----------------
> ...
> execution(* package3.SpecificClassNameHere.*(..))
> ...
> -----------------
>
> write:
> -----------------
> ...
> execution(* package3.SpecificClassNameHere*.*(..))
> ...
> -----------------
>
> then my class finally matches. But IMHO this is of course NOT, what one
> wants, since this could potentially also match other classes.
>
> Appears to be a bug in the pattern matching to me...
>
> Michael
|
|
|
|
Re: Problem with AspectJ syntax: "no match for this type name" [message #41935 is a reply to message #41904] |
Mon, 04 October 2004 15:08 |
Eclipse User |
|
|
|
Originally posted by: mchapman.uk.ibm.com
On Mon, 04 Oct 2004 16:38:44 +0200, Michael Moser wrote:
> I'm afraid, I have modified a different major "parameter" in the meantime
> (i.e. I installed 1.2M1 instead of 1.1.11) and in this version I don't see
> these problems any more. I hope that is "good news" for you even though we
> now haven't really nailed down that bug...
Hi Michael,
I guess it's good news, at least your upgrade made things better! We'll
have to see if anyone else encounters the problem on 1.1.11/1.1.12.
I will just add a note of caution - we haven't declared 1.2M1 as yet, as
we still have some fixes to make and testing to complete. You are running
a development build, which is hopefully close to the final 1.2M1 version.
Please still report any problems you find, but make sure you give the full
build identifier.
Regards,
Matt.
|
|
|
|
Re: Problem with AspectJ syntax: "no match for this type name" [message #583684 is a reply to message #41843] |
Mon, 04 October 2004 12:42 |
Matt Chapman Messages: 429 Registered: July 2009 |
Senior Member |
|
|
Hi Michael,
If you match against "Hello*.*" then you don't get a warning, but
if you do "Hello.*" you get the "no match for this type name"
warning, if the aspect cannot resolve the "Hello" type. So wildcards
are treated differently to absolute type names. In this case you
would need to tell the compiler which Hello you are referring so,
with something like "import foo.Hello;"
That doesn't however seem to completely explain the problem you are
seeing. The compiler is telling you it cannot resolve the
package3.SpecificClassNameHere class, despite it being qualified with
the package name. Could there perhaps be something unusual with your
project setup or layout? What happens if you refer to that class
from elsewhere in the aspect (from advice or a method)?
Regards,
Matt.
On Mon, 04 Oct 2004 12:41:12 +0200, Michael Moser wrote:
> BTW: I just noticed, that adding a "*" makes the problem go away:
>
> i.e. if I instead of
> -----------------
> ...
> execution(* package3.SpecificClassNameHere.*(..))
> ...
> -----------------
>
> write:
> -----------------
> ...
> execution(* package3.SpecificClassNameHere*.*(..))
> ...
> -----------------
>
> then my class finally matches. But IMHO this is of course NOT, what one
> wants, since this could potentially also match other classes.
>
> Appears to be a bug in the pattern matching to me...
>
> Michael
|
|
|
|
Re: Problem with AspectJ syntax: "no match for this type name" [message #583707 is a reply to message #41904] |
Mon, 04 October 2004 15:08 |
Matt Chapman Messages: 429 Registered: July 2009 |
Senior Member |
|
|
On Mon, 04 Oct 2004 16:38:44 +0200, Michael Moser wrote:
> I'm afraid, I have modified a different major "parameter" in the meantime
> (i.e. I installed 1.2M1 instead of 1.1.11) and in this version I don't see
> these problems any more. I hope that is "good news" for you even though we
> now haven't really nailed down that bug...
Hi Michael,
I guess it's good news, at least your upgrade made things better! We'll
have to see if anyone else encounters the problem on 1.1.11/1.1.12.
I will just add a note of caution - we haven't declared 1.2M1 as yet, as
we still have some fixes to make and testing to complete. You are running
a development build, which is hopefully close to the final 1.2M1 version.
Please still report any problems you find, but make sure you give the full
build identifier.
Regards,
Matt.
|
|
|
Powered by
FUDForum. Page generated in 0.02458 seconds