commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Carman" <>
Subject RE: Commons Metadata?
Date Tue, 07 Mar 2006 18:02:09 GMT
Well, that's the thing.  That's up to the "decorator" to decide how it gets
the metadata information.  Jakarta Commons Attributes does a pre-compilation
step to set up the .class files so that their attributes can be read from
them (from what I can glean from the docs).

-----Original Message-----
From: Thomas Dudziak [] 
Sent: Tuesday, March 07, 2006 12:57 PM
To: Jakarta Commons Developers List
Subject: Re: Commons Metadata?

On 3/7/06, James Carman <> wrote:

> I believe I brought this up before, but I really think there's a need for
> this.  We need a metadata framework which abstracts away the details of
> exactly how the metadata is found/provided.  For example, some
> use only JDK5 annotations to add metadata to their classes.  Others might
> use Jakarta Commons Attributes.  Others might want to use XML files (if
> don't want to have to touch the source).  So, what we could provide is a
> MetadataFactory (or whatever you want to call it) which can have "metadata
> decorators" added to it.  The decorators are added to a pipeline and are
> given a chance to append metadata information to the metadata object.  We
> created something like this for the Trails (
> so that we could use "off-the-shelf" domain models (how many times have
> seen those at Best Buy?) within the framework by providing metadata via
> files as opposed to using JDK5 annotations.  We could start this off in
> sandbox, of course.  Anyone interested in helping out?  I could start off
> developing the core classes (the metatdata "holder" classes).


That sounds useful, especially if it also can be used at compile time,
and if it can work with XDoclet-style Javadoc tags (e.g. using qdox or


To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message