Update of /cvsroot/xdoclet/xdoclet/modules/jdo/src/META-INF
In directory
sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv13785/modules/jdo/src/META-INF
Modified Files:
xtags.xml
Log Message:
- Updated jdo_2_0.dtd by the most current one from the JPOX project.
- Added/replaced some parameters of @jdo.field to match the current spec draft.
- Added docu (at least a stub) for each @jdo.field param.
Index: xtags.xml
===================================================================
RCS file: /cvsroot/xdoclet/xdoclet/modules/jdo/src/META-INF/xtags.xml,v
retrieving revision 1.11
retrieving revision 1.12
diff -C2 -r1.11 -r1.12
*** xtags.xml 15 Jan 2005 00:09:28 -0000 1.11
--- xtags.xml 21 Feb 2005 15:56:42 -0000 1.12
***************
*** 280,283 ****
--- 280,398 ----
<condition-description>Must be used with collection, map or array
valued persistent field, in case it is a double ended (or inverse)
relationship.</condition-description>
</parameter>
+ <parameter type="text">
+ <name>table</name>
+ <usage-description>
+ This parameter can only be used in JDO 2.0!
+ </usage-description>
+ <mandatory>false</mandatory>
+ <condition-description></condition-description>
+ </parameter>
+ <parameter type="text">
+ <name>column</name>
+ <usage-description>
+ This parameter can only be used in JDO 2.0!
+ It defines the name of the column into which this field
should be
+ persisted. You can use '@jdo.column name="xxx"' alternatively.
+ </usage-description>
+ <mandatory>false</mandatory>
+ <condition-description></condition-description>
+ </parameter>
+ <parameter type="bool">
+ <name>serialized</name>
+ <usage-description>
+ This parameter can only be used in JDO 2.0!
+ </usage-description>
+ <mandatory>false</mandatory>
+ <condition-description></condition-description>
+ </parameter>
+ <parameter type="bool">
+ <name>dependent</name>
+ <usage-description>
+ This parameter can only be used in JDO 2.0!
+ It controls whether to delete the object in this field if the
+ container object is deleted out of the store. Some people
+ call this behaviour 'cascaded delete'.
+ </usage-description>
+ <mandatory>false</mandatory>
+ <condition-description></condition-description>
+ </parameter>
+ <parameter type="text">
+ <name>value-strategy</name>
+ <usage-description>
+ This parameter can only be used in JDO 2.0!
+ It defines how to automatically assign values to this field.
+ This works in application identity and can be used to generate
+ values for one of the primary key fields.
+ Possible values that a JDO implementation might support are:
+ 'native', 'sequence', 'autoassign', 'increment', 'identity'
+ 'uuid-string', 'max', 'custom'
+ </usage-description>
+ <mandatory>false</mandatory>
+ <condition-description></condition-description>
+ </parameter>
+ <parameter type="text">
+ <name>delete-action</name>
+ <usage-description>
+ This parameter can only be used in JDO 2.0! Possible values
are:
+ 'restrict', 'cascade', 'null', 'default', 'none'
+ </usage-description>
+ <mandatory>false</mandatory>
+ <condition-description></condition-description>
+ </parameter>
+ <parameter type="text">
+ <name>indexed</name>
+ <usage-description>
+ This parameter can only be used in JDO 2.0! Possible values
are:
+ 'true', 'false', 'unique'
+ </usage-description>
+ <mandatory>false</mandatory>
+ <condition-description></condition-description>
+ </parameter>
+ <parameter type="bool">
+ <name>unique</name>
+ <usage-description>
+ This parameter can only be used in JDO 2.0!
+ </usage-description>
+ <mandatory>false</mandatory>
+ <condition-description></condition-description>
+ </parameter>
+ <parameter type="text">
+ <name>sequence</name>
+ <usage-description>
+ This parameter can only be used in JDO 2.0!
+ </usage-description>
+ <mandatory>false</mandatory>
+ <condition-description></condition-description>
+ </parameter>
+ <parameter type="text">
+ <name>foreign-key</name>
+ <usage-description>
+ This parameter can only be used in JDO 2.0!
+ </usage-description>
+ <mandatory>false</mandatory>
+ <condition-description></condition-description>
+ </parameter>
+ <parameter type="text">
+ <name>load-fetch-group</name>
+ <usage-description>
+ This parameter can only be used in JDO 2.0! It defines which
+ fetch-group should be used for loading the object in this
field
+ member.
+ </usage-description>
+ <mandatory>false</mandatory>
+ <condition-description></condition-description>
+ </parameter>
+ <parameter type="int">
+ <name>fetch-depth</name>
+ <usage-description>
+ This parameter can only be used in JDO 2.0! It defines, how
many levels the
+ JDO implementation should dive into the object graph for
detaching. This
+ is especially useful when an object contains a member of the
same class as
+ itself (or if there is an indirect circle).
+ </usage-description>
+ <mandatory>false</mandatory>
+ <condition-description></condition-description>
+ </parameter>
+
</tag>
<tag>
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
xdoclet-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
