Hi,

FWIW. I dont use Xcode, using WO 5.3.something for development. I dont get a stack trace in the WO exception page when not using direct connect(DC) but I do get a stack trace in the browser when using DC.

Chuck Hill wrote:
This just started in Xcode 2.4 / WO 5.3.2 (or is it 5.3.3 now?)?


On Nov 14, 2006, at 1:06 PM, Baiss Eric Magnusson wrote:

I also have this problem, I've let it pass because I throw all my exceptions to
    <WOResponse handleException>
but it has been a significant detriment.

I tried from Terminal's command line
    set WODebuggingEnabled true

And added to the Active Executable Arguments
-WODebuggingEnabled=true

But no stack...

From: Jean-Fran?ois Veillette     <[EMAIL PROTECTED]>

try : WODebuggingEnabled true



From: Chuck Hill <[EMAIL PROTECTED]>

I have seen this, or something like this, happen several versions ago
when the WOExceptionPage was shipped with an error in the .wo.  Check
the app logs and see if there is a reference to such an error.  Also
try creating and returning this page manually to see if you can find
the error.  The WOComponent Editor in WOLips might also be of help in
determining if this is the cause.

Chuck



The WOExceptionPage.WO validates.
In Console/Logs/console.log, I assume this is the <app logs>, I don't see the stack.


On Nov 13, 2006, at 9:28 AM, james o wrote:

I'm no longer getting detailed Exception Descriptions in my browser
window.  no Line#, File, Method, etc...  i'm using XCode 2.4
(downloading 2.4.1 now) on OS X Client 10.4.8 and WO 5.3.

help, it's become really difficult to locate my exceptions without
reference to any line or method.

----
Baiss Eric Magnusson
<http://www.Track-Your-Finances.com>
<http://www.CascadeWebDesign.com>





cheers,
 - shaun
_______________________________________________
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]

Reply via email to