Lists

Terms and Conditions
Lists hosted on this site
Email the Postmaster
Tips for posting to public mailing lists

Re: Why do Dynamic Elements get values from enclosing component in takeValuesFromRequest?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why do Dynamic Elements get values from enclosing component in takeValuesFromRequest?

Subject: Re: Why do Dynamic Elements get values from enclosing component in takeValuesFromRequest?
From: Mike Schrag <email@hidden>
Date: Wed, 25 Feb 2009 22:06:49 -0500
Delivered-to: email@hidden
Delivered-to: email@hidden

Why is there a necessity for the WOTextField to actually get() values from the enclosing component in a takeValuesFromRequest() stage of the request-response cycle?

validateTakeValueForKeyPath only pushes the value if it is different than the previous value (or if the previous or new value is a null), which requires getting the previous value first

ms

_______________________________________________
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: Why do Dynamic Elements get values from enclosing component in 	takeValuesFromRequest?
From: Karthik N <email@hidden>


References:  
  >Why do Dynamic Elements get values from enclosing component in 	takeValuesFromRequest? (From: Karthik N <email@hidden>)




Prev by Date:
Why do Dynamic Elements get values from enclosing component in 	takeValuesFromRequest?

Next by Date:
Re: Hibernate

Previous by thread:
Why do Dynamic Elements get values from enclosing component in 	takeValuesFromRequest?

Next by thread:
Re: Why do Dynamic Elements get values from enclosing component in 	takeValuesFromRequest?

Index(es):

Date
Thread

Apple Footer

This site contains user submitted content, comments and opinions and is for informational purposes only. Apple may provide or recommend responses as a possible solution based on the information provided; every potential issue may involve several factors not detailed in the conversations captured in an electronic forum and Apple can therefore provide no guarantee as to the efficacy of any proposed solutions on the community forums. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.

 Apple

Lists
Archives

More ways to shop: Visit an Apple Store, call 1-800-MY-APPLE, or find a reseller.

United States

Privacy Policy Terms of Use Sales and Refunds Legal Site Map