Steve--
Good catch -- while automatic generation of the shape for an
external override XML file could be a great feature to have, we don't
have that today (that I know of). Additionally, this annotation:
@AccessModes
doesn't exist in Controls any longer. The external overridability of
an annotation property value is specified via the
@AllowExternalOverride meta-metadata -- if you will. :)
We should fix that in this doc. Also, we should also remove
references to "JSR-175" metadata and just call it Java 5 metadata /
annotations (or just metadata / annotations). The JSR number isn't
that useful. :)
Eddie
On 1/12/06, Steve Hanson <[EMAIL PROTECTED]> wrote:
> Hi all:
>
> This section of the doc describes the generation of an XML schema on the
> compilation of a control:
>
> http://beehive.apache.org/docs/1.0/controls/overview.html#A+Flexible+Property+Model
>
> It claims that you can configure your control attributes through XML files
> that accord with the shema.
>
> Is this really true? I have noticed that there is an "externalConfig"
> property on the @PropertySet (
> http://beehive.apache.org/docs/1.0/apidocs/classref_controls/org/apache/beehive/controls/api/properties/PropertySet.html#externalConfig()
> ).
>
> But then the trail runs cold. If there is more to this trail, could someone
> fill me in. Otherwise I will cut this section from the doc.
>
> Thanks,
> Steve Hanson
>
>
