RE: [aspectwerkz-dev] Creating AOPified javadocs

It would be great if you could impl something like that.
Take a look at AspectJ's ajdoc, the output it produces.

Thanks.

/Jonas 

> -----Original Message-----
> From: the_mindstorm [mailto:[email protected]] 
> Sent: Tuesday, August 03, 2004 9:08 PM
> To: [email protected]
> Subject: Re: [aspectwerkz-dev] Creating AOPified javadocs
> 
> Hi!
> 
> If we can agree on what this tool is supposed to produce I 
> can start working on it (I have used QDox and it is pretty 
> nice [smile/]). What I have also unclear is how I can handle 
> the annotations a la 1.5. If I find a common point on the 
> above points I could start it asap (as my holiday is 
> approaching and I will have some more spare time [happy/]).
> 
> I will try later this evening to make some proposals but till 
> then feel free to propose yours.
> 
> [Have a nice day] / [10x]
> ---
> Pope
> ---
> <<There are only solutions...>>
> 
> 
> 
> Alex wrote:
> 
> > Hi
> > Speaking in terms of AOP, the concept of AspectJ ajdoc with some 
> > rewrite to fit the crosscutting annotations requirement 
> would probably 
> > be a nice fit.
> > Personnaly I think this kind of needs around annotations will be 
> > addressed by numerous tools in a near future.
> > (does someone knows what happens f.e. if in Intellij 4.5 
> with java 5 
> > support, I do a find usage of "foo" Annotation, it works fine ? - I 
> > guess it does !) If someone wants to start that by its own, we are 
> > using Qdox to parse java source code (f.e. in AnnotationC), 
> and this 
> > library is really good. Support for parsing Java 5 sources 
> (thus JSR 
> > 175 annotations) is beeing discussed.
> > Alex
> >
> >     ----- Original Message -----
> >     *From:* Guy Hacham <mailto:guy-usAmb/[email protected]>
> >     *To:* [email protected]
> >     <mailto:[email protected]>
> >     *Sent:* Tuesday, August 03, 2004 7:47 AM
> >     *Subject:* [aspectwerkz-dev] Creating AOPified javadocs
> >
> >     Hi,
> >
> >     I wonder if there is a way I can create documentation containing
> >     all the information about all classes and the relation 
> between them.
> >
> >     You can see it as AOPified javadocs that includes all the
> >     information from the xml and the annotations.
> >
> >     Rickard showed-off with a tool they have at
> >     
> http://jroller.com/page/rickard/20040302#static_crosscutting_rocks
> >     you can see the documentation example at
> >     http://www.senselogic.se/webdav/files/rickard/ForumId.htm
> >
> >     I think this is a great way to describe an AOP project 
> and I agree
> >     with Rickard saying "using static crosscutting in AOP can be a
> >     very powerful and useful design tool, but it more or 
> less requires
> >     that you have a good visualization tool in order to avoid
> >     confusion when using the objects".
> >
> >     Having a tool like this could be a great leap forward in using
> >     aspectwerkz in more complex environments.
> >
> >     Guy.
> >
>