>From the JRun developers guide: "The value of ejipt.createSQL generally contains a 'SELECT' statement that determines the validity of the object and returns the primary key, if necessary ... The ejipt.postCreateSQL generally contains an 'INSERT' statement." But if the record already exists in the database, what am I supposed to do so that JRun will throw a DuplicateKeyException, and not attempt the postCreate insert? If the createSQL select statement returns a row, then the ejb should not be created. I have included the "ejipt.isCreateSilent" env entry in the deployment descriptor and set it to False. I have noticed that it DOES throw a DuplicateKeyException if I first do a find on the primary key for that object. Any suggestions/comments would be appreciated. Thanks! ------------------------------------------------------------------------------ Archives: http://www.egroups.com/group/jrun-interest/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
