A simple way to access JavaDoc attributes at runtime
It’s easy to gain access to JavaDoc attributes using QDox, however this requires you to have the source available. At runtime this isn’t always possible, unless you’re happy giving your source away.
A workaround to this is to use QDox to parse the source code at development time and serialize the resulting structures to make them available at runtime. This will work, but it’s a bit nasty as big binary files aren’t the most stable of things.
A more open approach is to bundle the source of your classes with the application, making them available at runtime, however *without* the method body implementations.
*Class with method body implementations:*
package stuff;
public class CheeseSlicer {
/** @transaction mode=isolated */
public Slice feedMe() {
// some implementation specific stuff here.. don't waste your time reading it.
if (System.currentTimeMillisMillis() % 2 == 0) {
return new CheddarSlice();
} else {
return new BrieSlice();
}
}
}
*Class WITHOUT method body implementations:*
package stuff;
public class CheeseSlicer {
/** @transaction mode=isolated */
public Slice feedMe();
}
To do this is simple. First, QDox can be used to parse the source of a class into a JavaClass. Calling JavaClass.toString() will print out the class without the body implementations (as above). This is something done at development time and the result should be written to a file that is available at runtime.
At runtime, QDox can read this file just as if it were a full-blown Java source file, making the attributes available.
JDK 1.5, of course, makes this redundant, but in the mean time…
Joe Walnes 
Another idea is to use XStream instead, so you don’t get a huge binary file. But hey, you wrote XStre… ooooh… nevermind :))
also, http://metaclass.codehaus.org/ :)
Joe-,
Wake up, buddy – J2SE5.0 is here! With the latest snapshot they have bundled “apt”, which makes QDox very obsolete
Yes, please use a bloated XML format instead of a binary encoding. Java software is nowhere near slow enough yet.
Quick replies:
> Another idea is to use XStream instead,
That was considered too. But that’s another dependency. And serialization is much slower and more bloated.
> also, http://metaclass.codehaus.org/
Yup. There’s this too, which also provides a nice abstraction of meta-data, allowing another mechanism to be used than attributes. I was merely suggesting a lightweight approach that doesnt require another library and gives you access to the full JavaDoc model at runtime.
MetaClass is a more full featured solution.
> Wake up, buddy – J2SE5.0 is here! With the latest
> snapshot they have bundled “apt”, which makes
> QDox very obsolete
Absolutely. QDox is obsolete if using J2SE5.0. However I am still working on lots of project that are not using this yet, as are many other people. I imagine this will be the case for a while longer as well.
> Yes, please use a bloated XML format instead of
> a binary encoding. Java software is nowhere near
> slow enough yet.
Ermm… I don’t ever remember suggesting using XML :P. Using QDox to parse scan the source code is about TWICE as fast as native serialization, AND the file sizes are smaller, AND it’s plain text! So nurrrr.
> So nurrrr.
Nice conclusion.
Does java 1.5 make javadoc available at runtime?