From: Michael E. <men...@ez...> - 2004-07-30 14:12:10
|
Thanks for the help. I spent most of last night trying to figure out what is causing this and came up with this: 1) As Anjo suggested and I pretty much knew was the case, the 3rd party database dump that I get is inconsistent. To test to make sure this was the issue I generated fake data to fill iin the blanks and my problems went away. 2) The problem I was having is that ERXDatabaseContextDelegate was throwing the exception. After reading the javadoc (which I had done originally but somehow overlooked this aspect) I noticed that this class fixes a bug where a to-One relationship is not found. What was confusing me is that I didn't realize this class was used in place of the standard delegate supplied by WO. I couldn't figure out where this was getting loaded in by simply adding the framework to my application and not calling any code in the framework. As I said I don't think this is a bad thing but it's not self-evident that this is what is going to happen by just adding the ERX framework to a project. So in my current situation I can just fill the database with fake data (it's a simple table of just a foreign key and an text field so I can just generate the corresponding keys and put in empty strings or some other text). Now my two remaining questions are more for future reference are: 1) can I turn this off in the properties file for this framework? I tried most of the different settings and couldn't get it to work and 2) for this and other settings, can I just modify the framework properties file or is it best to override them in my application's property files. Thanks Mike On Jul 30, 2004, at 1:16 AM, David Teran wrote: > Hi Michael, > >> Am 29.07.2004 um 20:32 schrieb Michael Engelhart: >>> In this particular case I think this error is being thrown because >>> my EO has a relationship called PropertyDescription and the key >>> 222632 doesn't exist in that table. >> >> So your data is inconsistent? That looks like an error to me - either >> clear the entry or create a description with that ID. >> > > Do not know if your data is inconsistent or not but i had the same > problem on a running instance some time ago, too. The problem was that > some EOF always threw the EOObjectNotAvailableException even thought > the corresponding row was in the database. EOF even did not send any > SQL to the database. After restarting the app everything worked fine > again. I do not really know if your problem has something to do with > the erx but if you can reproduce it i would be happy about a demo. > Maybe we have a chance to debug this issue. > > regards David > |