• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: deprecated API
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: deprecated API


  • Subject: Re: deprecated API
  • From: Mike Schrag <email@hidden>
  • Date: Thu, 9 Feb 2006 16:45:02 -0500

For what it's worth, I do:

public WOActionResults someActionMethod() {
MyNewPage nextPage = (MyNewPage)pageWithName(MyNewPage.class.getName ());
nextPage.setSomeKeyName(value);
nextPage.setSomeOtherKeyName(otherValue);
return nextPage;
}


the class.getName() allows Eclipse to do proper refactoring and you can right click=>References=>Workspace your class and truly find all the refs vs just havign a string ref ... Minor change but really nice benefits.

ms

On Feb 9, 2006, at 4:40 PM, Chuck Hill wrote:

I usually do it the way that Jerry posted:

public WOComponent someActionMethod() {
MyNewPage nextPage = pageWithName("MyNewPage"); // 1
nextPage.takeValueForKey(aValue, "someKeyName"); // 3
nextPage.takeValueForKey(aValue, "someOtherKeyName"); // 4
return nextPage; // 5
}


'cept I usually avoid KVC unless I need it for dynamic reasons. I prefer the way that straight Java reads and the compiler checks don't hurt either.


Chuck


On Feb 9, 2006, at 11:46 AM, zac wrote:

What's your preffered method of initializing components?

Chuck Hill wrote:

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:
40mdimension.com


This email sent to email@hidden

_______________________________________________ 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
  • Follow-Ups:
    • Re: deprecated API
      • From: "Jerry W. Walker" <email@hidden>
    • Re: deprecated API
      • From: Chuck Hill <email@hidden>
References: 
 >deprecated API (From: zac <email@hidden>)
 >Re: deprecated API (From: Chuck Hill <email@hidden>)
 >Re: deprecated API (From: zac <email@hidden>)
 >Re: deprecated API (From: Chuck Hill <email@hidden>)

  • Prev by Date: Web Services, documented-style messaging
  • Next by Date: Re: deprecated API
  • Previous by thread: Re: deprecated API
  • Next by thread: Re: deprecated API
  • Index(es):
    • Date
    • Thread