If you mean the constructor being called by "INITIALIZE" then it looks like a bug.
On 2012-03-22, at 12:54 PM, Gino Pacitti wrote: > I am just trying to understand something about component and child component > behavior. > > I have a main component and three other components used in the page layout. > > PageWrapper (has the head and footer, nav etc) > > A Small Image Component > > A Link generating component > > There is no API connected in either the Small or Link Components although > PageWrapper has some logic attached. > > When I run the app the output shows that the Small component gets initialized > followed by the Link generator then the Main then the Page Wrapper and then > AGAIN the Small and then the Link? > > What controls the way in which the subcomponents are being generated - is > this a bug in my system or normal behavior > > 1. SMALL Component INITIALIZE > 2. Link generating INITIALIZE > 3. MAIN INITIALIZE > 4. PAGE WRAPPER INITIALISE > 5. SMALL Component INITIALIZE > 6. Link generating INITIALIZE > > Gino > _______________________________________________ > 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/chill%40global-village.net > > This email sent to [email protected] -- Chuck Hill Senior Consultant / VP Development 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/gvc/practical_webobjects
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ 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]
