On 9/Mar/2010, at 2:18 PM, Mike Schrag wrote:
> these don't look like actual exceptions, they just look like the stack traces
> from where the debug statement occurred ... these things should always say
> that in their exception message IMO
>
> On Mar 9, 2010, at 5:03 PM, Johan Henselmans wrote:
>> at
>> er.extensions.eof.ERXDatabaseContextDelegate.databaseContextDidSelectObjects(ERXDatabaseContextDelegate.java:343)
The comment from ERXDatabaseContextDelegate.java, circa line 343 says:
* This delegate method is called every time a fault is fired that needs
* to go to the database. All we have added is logging statement of the
* debug priority. This way during runtime a developer can toggle the
* logger priority settting on and off to see what faults are firing. Also
* note that when using {...@link ERXPatternLayout} one can set the option
to
* see full backtraces to the calling method. With this option specified
* a developer can see exactly which methods are firing faults.
It would appear that Wonder is helping you notice how your application is
accessing faults. If you research the incantation to turn off these messages,
you might consider submitting a patch which tells the next developer who hits
this what's going on and how to change it. ;-) Hey, at least you don't have
to set candles and draw a pentagram...
M.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
