Re: [Xdoclet-user] XDoclet vs Java annotations

pope Tue, 14 Dec 2004 15:13:53 -0800

[quote Jose Gonzalez Gomez::on 12/14/2004 2:51 PM]

Brian,

I sent it to [EMAIL PROTECTED] I'm currently testing my new
gmail account, so I'm subscribed using two mail addresses. I sent it
from my gmail address and I received it in my other mailbox without
any problem... maybe some misconfigured mail filter on your side?
Would you need me to send any message to the other list for testing
purposes, feel free to ask.

About the parser... I understand that if I would be interested in
doing something related, the right path would be to hack the QDox
project... is XDoclet2 completely decoupled from the source
annotation? I mean, if QDox would provide the same information to
XDoclet2 either using XDoclet tags or Java annotations, would XDoclet2
work without any change?

About reading .class files... I haven't read the specification that
much, but I got the feeling that you could access all the annotation
information using the reflection API, so I don't think that accessing
all the information that way would be more complicated than doing it
with XJavadoc or QDox, maybe I'm missing anything here...

The things here are not so easy. Actually the annotation retention policy (the way the compiler discards/preserves) annotation info is an enum with SOURCE, CLASS and RUNTIME. For the 1st case the annotation info is lost after a compilation. I know that for the RUNTIME this info can be retrieved at runtime using reflection, and unfortunately I am not sure what is happening with the 2nd type (it exists in the bytecode, but I think that reflection is not able to access it).

:the_mindstorm

What's the third thing? :o)

Best regards
Jose

On Tue, 14 Dec 2004 07:25:22 -0500, Brian Topping <[EMAIL PROTECTED]> wrote:

Hi Jose,

I didn't see this come across the X2 list, what address did you send
to?  Just want to confirm everything is operational...

What you are describing would work, but there are three components to
the problem.  The first one is a parser that can read annotated code.
X2 relies on the QDox project, and they are in the initial stages of
being able to accept code that has annotations in it.  I'm not sure
where or if they are going to make the code actually present the
annotations to the client, but I also don't know if that affects you.

The second is being able to read the .class file format for annotated
files.  This is a bit more work.  This could be done with runtime
reflection on the classfiles in a JDK 1.5 environment, but work would be
required to make the tool run under the different combinations of
supported versions and build packaging to support that.

It will come, but there's nobody currently working on it (feel free to
look at it though! :-)

-b

Jose Gonzalez Gomez wrote:

>  Hi there,
>
>  I sent this yesterday to the XDoclet2 list but nobody answered...
>I'm posting it here in the hope that somebody comments it, as I also
>think that this is applicable to XDoclet1...
>
>  First of all, this doesn't intend to be an attack to XDoclet, I've
>been using it for a long time and I've been quite pleased with it.
>Having said this, let's begin the criticism ;o)
>
>  I have recently come across a problem that it doesn't seem to have
>an easy or elegant solution: I was using maven to create a domain
>model containing classes persisted with Hibernate, and I splitted the
>model so I could have some reusable abstractions tagged with
>@hibernate tags. The problem is that when I used the Hibernate doclet
>to generate the mapping files I wasn't successful... why? Evidently
>because dependencies are commonly resolved using precompiled jars (at
>least in maven) and XDoclet didn't have access to the source files of
>the dependency containing the reusable abstractions.
>
>  As I told you before, I don't see an easy or elegant way of solving
>this other than including the source files of the dependency so
>XDoclet has access to them... why do I talk about Java annotations in
>the subject? Well, because, from my limited understanding of Java
>annotations gathered after a quick reading of the release notes, it
>seems that this could be easily solved if instead using XDoclet tags
>you used Java annotations. Java annotations seems to be an special
>kind of "interface" (take this with a bit of salt) so the annotation
>information seems to travel with the bytecode of the Java class and is
>accessible using the reflection API. So it seems you could have access
>to the annotations even if you don't have access to the source code of
>the dependency... am I wrong? If this is correct, my problem would be
>gone easily...
>
>  Best regards
>  Jose
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now.
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>xdoclet-user mailing list
>[EMAIL PROTECTED]
>https://lists.sourceforge.net/lists/listinfo/xdoclet-user
>
>
>
>

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user

------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user

Re: [Xdoclet-user] XDoclet vs Java annotations

Reply via email to