Try this: Override appendToResponse in the component. Then wrap a call to super.appendToResponse() in a try/catch and log in the catch.
On Jul 1, 2013, at 12:36 PM, Jesse Tayler <[email protected]> wrote: > thanks K- > > shouldn’t it be giving a backtrace whatever it is? > > I was wondering if it were automatic builds or unsaved files, but it seems > like I’m able to update things and retest as I’d expect. > > the method in question performs a fetch through a relationship, but I don’t > see why that’s unusual or why I’d not get any backtrace? > > > > On Jul 1, 2013, at 12:17 PM, Kieran Kelleher <[email protected]> wrote: > >> Might be classpath: The classpath in development is not the same as the >> classpath in deployment. >> >> >> On Jul 1, 2013, at 11:04 AM, Jesse Tayler <[email protected]> wrote: >> >>> >>> I have an odd situation, perhaps it rings bells with someone ? >>> >>> I have a method which in deployment causes an exception, but I don’t see >>> any report in the backtrace? >>> >>> I can see the new method that trips the error, but I cannot figure or >>> reproduce the error in development. >>> >>> If I remove the bindings from the component, the app runs normally, but >>> when I return the bindings, the method trips and I get an error with no >>> backtrace and only on my deployment server. >>> >>> any thoughts on that? >>> >>> >>> >>> _______________________________________________ >>> Do not post admin requests to the list. They will be ignored. >>> Webobjects-dev mailing list ([email protected]) >>> Help/Unsubscribe/Update your Subscription: >>> https://lists.apple.com/mailman/options/webobjects-dev/kelleherk%40gmail.com >>> >>> This email sent to [email protected] >
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
