Re: deprecated API
Re: deprecated API
- Subject: Re: deprecated API
- From: Chuck Hill <email@hidden>
- Date: Thu, 9 Feb 2006 11:35:13 -0800
WOComponent, right? The constructor that you should call is the one
taking a WOContext as its sole parameter. This is the one called
when pageWithName() is used. I'm not sure if there are any potential
bad side effects of constructing a top level page manually as opposed
to using pageWithName. You might be better off adding a static
method to use as a constructor. That can call pageWithName and then
set the parameters.
Chuck
On Feb 9, 2006, at 11:20 AM, zac wrote:
I'm an old java hack who is picking up webobjects. When I try to
overload a component's default constructor I get build warnings
about overloading a deprecated api. I'm wondering what the best
practices policy is for initializing components with more than one
set of parameters.
Thx,
Zac
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40global-village.net
This email sent to email@hidden
--
Coming in 2006 - an introduction to web applications using WebObjects
and Xcode http://www.global-village.net/wointro
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