I think all these things interesting for reflection or meta programming. It is a problem with metadata at compile time, compiler must be customized to add metadata ( attributes ) for classes and methods, I think preprocessing or XML stuff generation from source is not a very good solution, but it is not trivial to implement java compiler and it will be out of scope for this project. There are some opensource compilers like http://pizzacompiler.sourceforge.net/, we can start some project for compiler in sandbox too, is it can be usefull ?
> Folks, > > I think there are at least four parts to what we ultimately expect from > this: > > 1. A way to capture some type of meta model. For instance, JavaBeans > describe objects in terms of Types and Properties (scalar or indexed). > > 2. A way to extract a meta model from Java runtime. That's where the > mapping of method names to properties and all that stuff comes in. > > 3. A way to customize the meta model extracted from Java runtime. We > want to be able to bend or redefine the mapping rules. > > 4. A way to use the meta data to manipulate objects and object graphs > in a generic fashion. I am talking about methods like > get(propertyName), set(propertyName), add, remove etc. > > Are all these four things addressed between [reflect] and [clazz]? > > - Dmitri > > __________________________________________________ > Do you Yahoo!? > Y! Web Hosting - Let the expert host your web site > http://webhosting.yahoo.com/ > > -- > To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:commons-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:commons-dev-help@;jakarta.apache.org>
