Serethos,
As far as I know your approach is generally impossible. Nesting one
component as an inner class of another seems to me that it would
totally screw up WOContext and the entire request-response cycle.
The errors you are seeing are likely due to WO context confusion. WO
is going to look in your page cache for components using the
WOContext, which I'm guessing is getting mangled by the nested classes.
I don't see why it's a problem to leave Main a normal WOComponent and
add a separate page to your project that subclasses
WOLongResponsePage and do your long processing there. Then when
complete just return back to Main as the resultPage().
If you choose not to fight the system you'll be a happier programmer.
On May 2, 2007, at 9:36 AM, [EMAIL PROTECTED] wrote:
Thx for your reply. The main problem is that I am fully aware of
using the LRP in a different (and definitely
crappy) way. The main question for me is, if my way is generally
possible, therefore I have to understand
the errors, which occur.
In your example terms I want to achive that A contains the main and
long processing code, which can/shall
_not_ be moved into B. I know, there are several ways and easy
methods to get a clear design which would
follow apple's example. But for now I have to focus on a bad
design. The inner class is the main quick&dirty
idea of leaving the long processing code int A but starting it
within B (possible through the easy and full
access to the enclosing A class).
_______________________________________________________________
SMS schreiben mit WEB.DE FreeMail - einfach, schnell und
kostenguenstig. Jetzt gleich testen! http://f.web.de/?mc=021192
--
Robert Walker
[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:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
