0 Replies Latest reply on Mar 21, 2006 11:41 AM by nickthegreat

    odd @verison behaviour


      started an ejb3 project / persistence layer/unit without @version annotion.

      tried the @version annotion today with the following very strange result:

      after deployment the schema update worked fine, the optlock/version column got created with default values null.

      now it gets strange: whenever an object got "touched" (by SLSB's) it got duplicated(!) in db with version property set to 0 ???

      What's going on here ?
      Anyone any idea ?
      Bug or feature :) ?
      HEM dokumenation is rather minimalistic with respect to this annotation.

      I dont need it for my current EJB3 project, so this hab been a just for fun attempt .. but it's really puzzles me ...

      tia for infos, regards, ntg.