|
Thanks Peter, I've got another question regarding the generated
repository_user.xml. It includes fields like the following in every
class: <field-descriptor column="traLockTimestamp" jdbc-type="TIMESTAMP" name="lockTimestamp"/> <field-descriptor column="traLockUser" jdbc-type="VARCHAR" name="lockUser"/> <field-descriptor column="traLastModified" jdbc-type="TIMESTAMP" name="lastModified"/> <field-descriptor column="traLastModifier" jdbc-type="VARCHAR" name="lastModifier"/> Can you explain why they are there? Is there any part of OJB that would make use of them? I can see that (if there was an option in AXgen for it) the lockTimestamp field could be used for optimistic locking, but the other fields appear to be specific to some other use expected by AXgen. Thanks. Peter Wieland wrote: Hi Larry, I'm not sure wether I can help you but at least I can explain you how AXgen makes sure the DDL will meet the needs of OJB. Both, the OJB repository.xml and the DDL are generated based on the same UML model (the XMI). The templates make sure that the table definitions in the DDL and the definitions in the OJB mapping use the same types.I never tried to generate the DDL from the repository directly as we model all of our classes, we never needed such a feature. Modelling entities in a case tool and use this model as input for all generation works very well. Regards, Peter --
Senior Vice President and CTO
| ||||
<<inline: HL_PMS_smaller.jpg>>
