Typed Context APIs Vs Generic APIs

[Former Member]

Hello Gurus,

I would like to have your views on using typed context and generic apis in the webdynpro code? When to use these APIs? Is there any additional benefit of using Generic APIs in terms of Performance, memory consumption etc.

Would love to hear from you?

Abhinav

[Former Member · Accepted solution]

Hi expert,

Context api is use fullfor creating value node and attribute at design time where as generic Api is use full for creating Value Node and attribute at Run time proceess ,it very use ful atrun time..

context Api is static purpose and Generic api is dynamically created,,,,

Type context Api is Known to user and Generic Api are unknown to user....

Type context Api---I<node name>Element(),currentContextElement().get<attribte Name>();

Generic Api--IWDNodeElement,

hope you will get clear ..

thanks

jati

[Former Member · Accepted solution]

That's nonsense.

Armin

[Abhinav_Sharma · Accepted solution]

Hi..

Thanks for replying. one last question: Is there any immediate benefit of using any of these two? This may sound stupid but is there any improvement in memory usage or performance using generic APIs in compare to typed one?

Abhinav

[Former Member · Accepted solution]

The typed API causes a slight memory overhead. If you deselect "typedAccessRequired", less code is generated.

Armin

[Former Member]

I would say use the typed API whenever possible, also if it causes some overhead in the amount of generated code and some small runtime overhead.

Armin