> The vendor extension elements should end up in different places with field
> and collection tags. If not, can you demonstrate just what happens?
Ok, I see the motivation now. For the extensions I'm using, they go inside
the <field></field> block. So the @jdo.field-vendor-extension tag is all
that is needed. I'm not aware of it, but I suppose there could be
extensions that'd only be valid inside tags that are inside the <field>.
For example:
<field name="monitors"
>
<collection
element-type="Monitor"
>
<extension vendor-name="kodo"
key="some-extension-that-must-be-inside-the-collection-tag"
value="value">
</extension>
</collection>
<extension vendor-name="kodo"
key="element-dependent"
value="true"> </extension>
</field>
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. www.etnus.com
_______________________________________________
xdoclet-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-user
