life span property

[Former Member]

hi,

can any one tell me what is the use of lifespan property in webdynpro.....what is its use?

thanks & regards

vijaya

[Former Member]

vijaya,

In addition to answers about life span of components (top-level or component usages), here is info regarding lifespan of view.

View has 2 life span options: framework-controlled and when-visible.

First option forces laizy initialization of view on first use (when view become visible); afterwards view is kept alive and stays in memory until corresponding component is destroyed. So you may quickly navigate back and force between this view and other views, and view will keep state you left it at.

When-visible option forces view initialization when view becomes visible and view destruction when view becomes invisible (most typically when you are navigating from this view or from view assembly this view is participating in). Every time you navigate to such view its state is discarded.

Valery Silaev

SaM Solutions

http://www.sam-solutions.net

[Sharadha1]

Hi Vijaya,

The lifecycle of a component interface controller is based on the Lifespan property of the corresponding component usage. This property can have the value createOnDemand or manual.

For component usages of type createOnDemand, the Web Dynpro runtime environment automatically instantiates the component interface controller (and visible components of the component interface view controller) when necessary.

For component usages of type manual, the application developer controls the component interface controller lifecycles using the IWDComponentUsage interface.

Regards,

Sharadha

[venkatakalyan_karanam]

Hi

All webdynpro components are under the control of an application ,The lifespan of a component cannot exceed the lifespan of the application that invoked it.

component instantiation

==================

1.Applications root component ,its invoked by webdynpro framework(WDF) and lifespan is equal to that of application

2.A child within some other parent component ,here instantiation is controlled by lifespan parameter in the component usage declaration.If this param is set to createOnDemand, in which case the comp is instantiated by WDF or it is set to manual in which case you are responsible for instantiation.

Component terminates when app is closed or when parent component decides that no longer requires the child comp instance and disposes it manually

regards

kalyan