Re: [aspectwerkz-dev] Creating AOPified javadocs

Hello Alexandru

After reading Alex's comments, I think I got some points. If something
wrong, please correct me, Alex.

The key of this problem is when to collect aop model information and
who will supply these information. Two solution list here:

1.javac + weave classes + generate stubs and javadoc  [method 1 and
method with emitted join points]
2.parse sources + generate stubs and javadoc

And I divide AW engine workflow into five phrase(maybe more,but here
I think five is enough).
1.hook phrase      : pipe BootClasspathStarter/JDWPStarter after
java.lang.ClassLoader
2.preProcess phrase: initialize preProcessor,filter certain CL and modify CL
3.parse phrase     : parse xml and javadoc @tags
4.compile phrase   : compile Java source
5.transform/weave phrase: weave the cross-cutting info

diagram like this:
(see attached file)

Let's discuss solution 2 first. We should parse java sources by
ourself using QDox, then parse xml def, finally we structure aop
domain model by our hand. This solution is better to me first
impression, because I dream he can avoid "compile phrase". But maybe
it's my daydream.

And if we refer to solution 1, "compile phrase" has to be involved,
but we can access aop domain model easily through weaver context.


/Jack