[#GDS-537] Tide: lazy initialization should not use ItemPendingError - Granite Data Services

GraniteDS

Tide: lazy initialization should not use ItemPendingError

Created: 14/Oct/09 01:38 AM Updated: 03/Feb/10 01:24 PM Resolved: 14/Oct/09 01:43 AM

Component/s:

Tide

Affects Version/s:

None

Fix Version/s:

2.1.0_RC1

Description

« Hide

Due to the way it's handled in Flex components, ItemPendingError should probably be used only for paging.
This should also allow using lazy loading in Tree components.

Sort Order:

[ Permalink | « Hide ]

Galen Dunkleberger added a comment - 02/Feb/10 09:17 PM

Can I assume that with this fix the documentation for "Manually Fetching Lazy Collections" located at http://www.graniteds.org/confluence/pages/viewpage.action?pageId=9371685 no longer applies? Are there plans to somehow still support manual fetching of lazy collections. We ran into a use case on my project where we needed to manually fetch a lazy collection but could not figure out how to do it without the ItemPendingError.

[ Permalink | « Hide ]

William Draï added a comment - 03/Feb/10 12:53 PM

See updated doc for 2.1:
http://www.graniteds.org/confluence/pages/viewpage.action?pageId=15466513

[ Permalink | « Hide ]

Galen Dunkleberger added a comment - 03/Feb/10 01:24 PM

Thanks I should have looked at the doc updates first.