Re: [Worked]: In WOComponent constructor and need to go to another WOComponent and not come back
Re: [Worked]: In WOComponent constructor and need to go to another WOComponent and not come back
- Subject: Re: [Worked]: In WOComponent constructor and need to go to another WOComponent and not come back
- From: Chuck Hill <email@hidden>
- Date: Tue, 4 Sep 2007 20:27:55 -0700
I just can't see how that could ever, ever be an acceptable design.
You have a piece of code in Discuss.java that just flat out does not
want to be there. Find a new home for, some place it belongs. In
the long run, you will b both be happier.
Chuck
On Sep 4, 2007, at 7:36 PM, Baiss Eric Magnusson wrote:
I let the Constructor set a <validPage> boolean.
Discuss discussPage = (Discuss)pageWithName("Discuss");
return ( discussPage.validPage() ? (WOComponent)discussPage :
gotoAdmin() );
On Sep 4, 2007, at 6:22 PM, Chuck Hill wrote:
On Sep 4, 2007, at 5:41 PM, Baiss Eric Magnusson wrote:
I'm in the Constructor of a WOComponent sub-class and I realize I
have to be in another page.
I invoke a new <pageWithName>, but then what?
Change your design, know before. Maybe move the decision to a
"page flow" class.
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve
specific problems.
http://www.global-village.net/products/practical_webobjects
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
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