Re: [aspectj-users] Type not exposed to the weaver

[Adrian Colyer <adrian_colyer@xxxxxxxxxx>]

You can..... by putting type on the "inpath" rather than the "classpath" - 
but you want to check the license conditions of any binary jar file 
distributed by a third party before you do things like this (I think 
there's an FAQ on point, but I'm disconnect now so I can't dig up a 
reference for you).

It's not uncommon to get confused about the difference between classpath 
and inpath in these situations:

* classpath is used to resolve types so that they are visible to the 
compiler 
* inpath is used to tell the compiler/weaver that a class should be woven 
into

So a class on the classpath will be 'seen' by the weaver from a 
type-resolution perspective, but will not be affected by the weaving 
process.

-- Adrian
Adrian_Colyer@xxxxxxxxxx



Mohammed Al-Mansari <m_a_almansari@xxxxxxxxx> 
Sent by: aspectj-users-admin@xxxxxxxxxxx
12/09/2004 15:12
Please respond to
aspectj-users@xxxxxxxxxxx


To
aspectj-users@xxxxxxxxxxx
cc

Subject
[aspectj-users] Type not exposed to the weaver






Hi all,
I apologize if my question is old...
 Can I weave a java library .class file? e.g. can I introduce the 
java.util.Calender to implement MyInterface?
 
import java.util.*;
...
declare parents: Calender implements MyInterface;
 
I have tried it out but I got:
 
warning this affected type is not exposed to the weaver: 
java.util.Calender [Xlint:typeNotExposedToWeaver]
 
how can I expose it to the weaver other than importing it?
 
thanks in advance!
 
mohammed
Do you Yahoo!?
Shop for Back-to-School deals on Yahoo! Shopping.