Re: WOLongResponse Page Kills Main Thread
Re: WOLongResponse Page Kills Main Thread
- Subject: Re: WOLongResponse Page Kills Main Thread
- From: Jonathan Miller <email@hidden>
- Date: Mon, 28 Jan 2008 19:03:55 -1000
Nothing is getting written to the /tmp/ApplicationName-1
Is there another location I should be looking at?
re: Wonder version 3.0 Yes. I'm creating and saving some EOs. I
just create a new Editing Context for those operations, everything
gets written to the database normally. After the database edits, I
send a couple auto-generated emails. They get sent.
The last operation that should take place before the pageForResult is
just a System.out - and that gets written to the console.
Thanks for your help,
Jon
On Jan 28, 2008, at 5:17 PM, Guido Neitzer wrote:
On 28.01.2008, at 19:12, Jonathan Miller wrote:
Inside the performAction method is a switch statement. On two of
the cases the WOLongResponse behaves normally and returns the
result page. On the other hand on only one of the cases it goes
through all the business logic of that case (even a simple logging
statement called right before the break) but then does not fire the
pageForResult method. The return for performAction is put outside
the switch statement.
Without actually seeing code or a stacktrace from the hanging app,
how should we know?
There are no error messages. Everything works normally in
development mode. This is my first WONDER application, is there
anything I should be aware of when using WOLongResponse and WONDER?
Which Wonder version? Are you working on any EOs on that page? Do
you have them in a separate editing context? Where are you accessing
them if you do?
cug
--
Real-World WebObjects class at the Big Nerd Ranch
March 2008, Frankfurt, Germany
http://www.bignerdranch.com/classes/webobjects.shtml
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden