<element ..>
.....
<content schema-id=""
or service-id=""
or configuration-id=".."
parentMethod=".."/>
</element>The content tag would just mean that the content of the element would be parsed/validated according to the specified schema. The resulting List would be given to the parentMethod.
The service-id and configuration-id attributes are there in case the referenced schema doesn't define an id.
This would alow much more flexible setups. Ie if it is recursively applied BeanFactory could profit.
However as said I don't know if this is hard to implement. I don't realy get this schema code 8-).
Thanks, Chris
-- Christian Essl
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
