> <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. You're right, these fields are not required or used directly by OJB. The lock timestamp and lock user fields were in fact meant to enable optimistic locking. The last modified and last modifier fields are used quite similar by the developers to track data modification (via an OJB interceptor). In fact the templates included in OJB are meant to be examples and it is quite easy to adopt them to any projects personal needs. So once again, the fields you describe are not required by OJB. You may either use it at your will, ignore it or change the templates in which case you would probably need to provide your own super-interface (replacing de.armax.base.datasource.AXentity in AXentity.jar). Regards, Peter --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
