The problem is we have PL/SQL scripts (or equivalent) that trap referential and null constraint violations on data from external sources. In that sense the presense of a bad foreign key is not an "exception" but a normal event. If we let those bleed through the application we will get exceptions galore. We can explicitly test for nulls in the import code or let them bleed through and query for them after the fact. Those are possible solutions but sub-optimal when you consider that moving the commit from after ejbCreate to after ejbPostCreate solves the problem for all target databases and eliminates having to change existing applications across the board. Anyhoo, thanks for the response.
-----Original Message----- From: Gavin Matthews [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 05, 2003 11:36 AM To: '[EMAIL PROTECTED]' Subject: RE: [JBoss-user] The JBoss Deferred Constraint Requirement Issue Rod, I believe what you want is to make the CMR column nullable (in ejbCreate JBoss inserts the row with the CMR field set to null). This is then updated after ejbPostCreate(). Another option would be to set sync-on-commit-only to true but this breaks some of the spec compliance (finders cause sync) and also unless you're careful may cause logical problems. hope this helps, gavin -----Original Message----- From: Rod Macpherson [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 05, 2003 11:18 AM To: [EMAIL PROTECTED] Subject: [JBoss-user] The JBoss Deferred Constraint Requirement Issue Background JBoss executes a commit between ejbCreate and ejbPostCreate but we do not add CMP relationships until ejbPostCreate. This can cause create to fail when there are foreign key constraints. One solution is to defer constraint checking until after the transaction completes. WebLogic has a different approach in that they do not commit until after ejbPostCreate and this simplifies things in my opinion. Having started out in WebLogic we had to change our database configuration to use JBoss and we were able to do that without incident. Problem The problem has resurfaced now that we have a customer whose schema is hosted by SQL Server. Apparently there is no way to defer constraints on that system. Any ideas on a workaround short of eliminating constraints altogether? TIA, Rod ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01 /01 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
