Re: [aspectj-users] Re: no match for this type name...

[Ramnivas Laddad <ramnivas@xxxxxxxxx>]

I will take this task.

-Ramnivas

--- Wes Isberg <wes@xxxxxxxxxxxxxx> wrote:
> Hi Ramnivas -
> 
> That's a great suggestion!: a document that lists the
> interpretation and possible solutions for each compiler message.
> We could fold that into the FAQ immediately, and into the
> ajc section of the Development Environment Guide with
> the next release.
> 
> Does anyone care to submit a draft?
> 
> Thanks -
> Wes
> 
> 
> Ramnivas Laddad wrote:
> 
> > Michael,
> > 
> > No problem. I am glad that you could get the example 
> > to work.
> > 
> > Once you get over the initial bump in using AspectJ,
> > I assure you that you will have a smooth ride ahead. 
> > In the end, time saved by using AspectJ will compensate 
> > for time spent in learning it and then some!
> > 
> > For the error message, how about something like:
> > "Unknown type MessageCommunicator. Please ensure correct 
> >  spelling and/or the type is visible to the source file
> >  (check your import statements or use the fully-qualified 
> >   type name)".
> > 
> > The downside I see is sheer verbosity of the message.
> > Perhaps a better alternative is to point to document
> > that elaborates on "Xlint:invalidAbsoluteTypeName".
> > 
> > Thanks for your positive comments on my book.
> > 
> > -Ramnivas
> > 
> > --- Michael McConnell <mcconnellem@xxxxxxxxx> wrote:
> > 
> >>Raminvas --
> >>
> >>Thanks for the tip, I realized it later after sending the note. And
> I
> >>apologize for my
> >>asperity. In my opinion, the error message itself leaves a lot to
> be
> >>desired.
> >>
> >>Actually, I am enjoying your book quite a bit -- I think it is very
> >>well written and
> >>understandable (up to the problem I encountered). 
> >>
> >>I got frustrated because AOP techniques could be used very
> >>successfully at my engagement,
> >>my time is extremely limited, and to have show stoppers like this
> >>without any pointers on
> >>where to look to fix it, were very maddening.
> >>
> >>Again, I appreciate your tip and your book.
> >>
> >>Regards,
> >>Michael
> >>--- Ramnivas Laddad <ramnivas@xxxxxxxxx> wrote:
> >>
> >>>It seems that your HindiSalutationAspect is in 
> >>>the default package, whereas MannersAspect and 
> >>>MessageCommunicator is in helloWorld package. 
> >>>That is the reason you need to import MessageCommunicator 
> >>>class in one case and not the other.
> >>>
> >>>Please try adding "package helloWorld;" to HindiSalutationAspect
> >>>and let us know the result. You shouldn't need to import
> >>>MessageCommunicator in that case.
> >>>
> >>>-Ramnivas
> >>
> >>
> >>
> >>=====
> >>
> >>
> >>
> >>	
> >>		
> >>__________________________________
> >>Do you Yahoo!?
> >>Friends.  Fun.  Try the all-new Yahoo! Messenger.
> >>http://messenger.yahoo.com/ 
> >>_______________________________________________
> >>aspectj-users mailing list
> >>aspectj-users@xxxxxxxxxxx
> >>http://dev.eclipse.org/mailman/listinfo/aspectj-users
> > 
> > 
> > 
> > 
> > 	
> > 		
> > __________________________________
> > Do you Yahoo!?
> > Friends.  Fun.  Try the all-new Yahoo! Messenger.
> > http://messenger.yahoo.com/ 
> > _______________________________________________
> > aspectj-users mailing list
> > aspectj-users@xxxxxxxxxxx
> > http://dev.eclipse.org/mailman/listinfo/aspectj-users
> > 
> 
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/aspectj-users



	
		
__________________________________
Do you Yahoo!?
Friends.  Fun.  Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/