> From: Rich Wagner [mailto:[EMAIL PROTECTED] > > Have you considered using reflection, in addition to meta-model files? In > other words, imagine searching Ant's classpath for task classes, and then > using reflection to (for instance) discover what attributes each task > class accepts.
Actually, instead of duplicating the reflection code in Ant, use the Ant API itself. We have recently improved IntrospectionHelper to expose all attributes and elements and extension points (add(X) methods) supported by any bean (task/type/etc...), including whether it accepts nested text. Now with AntLibs, you can also auto-discover tasks/types by scanning the classpath for antlib.xml resources, which is the most often used way to declare an AntLib such that is works with the antlib:package.name magic namespace URIs (it then expect a package/name/antlib.xml resource). >From the antlib.xml resources, you can know which classes to load and feed to IntrospectionHelper to find out everything about them in terms of attributes/elements/extensions-points/text supported. Just my 2 cents. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
