From: Farrukh N. <fa...@we...> - 2009-04-29 14:35:39
|
Hi Nicolas, Unfortunately, the current code base does not support this level of control on versioning. Nicolas _ wrote: > Hi! > I have enabled versioning, and I have a little problem. I have created > an object type with an integer attribute (i.e. an Slot) that is > incremented from time to time. The point is that I do not want a new > version of my objects to be created each time that attribute is > updated. In principle, I could make the Slot refer to a kind of > counter object. In this way, if I update the counter, the main object > is not affected and no new version is therefore created. For this to > really work, I need to enable versioning for my main object type, and > not for the counter type. The problem is that both extend > ExtrinsicObject, so if in the? omar.properties file I define > ExtrinsicObjects as versionable, my solution does not work. I tried > specifying in omar.properties my main object type, instead of > ExtrinsicObject, but it does not work. I found that the problem in the > loadVersionableClasses() method of the VersionProcessor class. There, > an attempt is made to load > "org.oasis.ebxml.registry.bindings.rim.MyObjectType", which does not > exist. So it seems that only canonical object types can be defined to > be versionable (and then all their extensions will be), but specific > extension cannot. > I would appreciate any help on how to achieve what I want. Thanks! -- Regards, Farrukh Web: http://www.wellfleetsoftware.com |