Re: [aspectj-dev] weaving information via messages

[Martin Lippert <lippert@xxxxxxx>]

Hi Mik,

> > > I'm not sure if AJDE is set up to provide in-process signals or 
> > > surface a partial structure model before a compile has completed.  
> > > If it is, we should use that.  If not, we should consider whether 
> > > that's where we should be putting these efforts.
> >
> > Good point. I already thought that the AJDE people might have to solve 
> > a similar problem: find out, which aspect is woven into which class. 
> > How do they generate that information?
>
> The weaver generates that dependancy information and places it in the
> structure model (org.aspectj.asm).  Currently a full build of the world is
> required to build a model with crosscutting structure.  It shouldn't take
> you long to make an API that exposes that structure as a dependency table. 
> Let me know if you would like some help.
>
> Writing of class files is the only part of the compile that you could skip
> easily if all you're after is a correct structure model.  We can add a flag
> indicating that the compiler should be in model-building mode.  That'll be
> useful for testing as well.
>
> Let me know if I've overlooked any issues you need to know more about
> before going forward.

Before I start looking at it just a short question: I use only the weaving part, 
as you know, for my load-time weaving for the Eclipse system. Therefore I weave 
class per class. And I need the structure information for after each single 
class that is woven. Do you think it would be possible to use the structure 
model for this kind of single-class-weaving?

If so, what do I have to do to set up and reset the structure model for the 
weaver/world? (Because I do not use the real compiler or builder parts)

Best regards,
Martin

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature