ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jesse Glick <Jesse.Gl...@netbeans.com>
Subject Re: [DISC] details of task library concept
Date Wed, 23 May 2001 12:21:11 GMT
Not in response to any particular message but:

Has anyone given thought to optional task (type, ...) metadata classes in Ant
2.0? For example, in the JavaBeans spec, you can provide a "raw" bean with
getters and setters and so on and rely 100% on introspection to discover its
structure. But you may also supply a BeanInfo that gives more information on
properties, events, etc.

Maybe this could be useful for Ant tasks as well. For example, something like
the following model:

- task developer supplies a BeanInfo class for the task (so that
java.beans.Introspector can be used to find it using standard mechanisms)

- the BeanInfo can implement some interface AntInfo extending BeanInfo, with
method e.g. getAntDescriptor

- Ant includes some utility method to generate an introspected AntInfo if none
is provided by the task

- AntDescriptor extends FeatureDescriptor but is intended to replace
IntrospectionHelper: description of available properties with correct Method
correspondences (PropertyDescriptor's?), optional method for adding CDATA text

- types of properties are classes, which can themselves be described via
AntInfo recursively, as IntrospectionHelper does now

- AntDescriptor can specify a display name/tooltip/icon/... useful for GUI
environments, documentation autogeneration, etc.

Would it be useful?

-Jesse

-- 
Jesse Glick   <mailto:Jesse.Glick@netbeans.com>
NetBeans, Open APIs  <http://www.netbeans.org/>
tel (+4202) 3300-9161 Sun Micro x49161 Praha CR

Mime
View raw message