Directly accessing the client side cookies in Web Dynpro is not support becuase it breaks the abstraction layer and may not be compatible with future releases nor would it be compatible with the NetWeaver Business Client Smart Client Rendering or the Flex Client Rendering.
Direct access to the cl_wdr_task object is also not supported by SAP. Such access can lead to inconsistences and future incompatibilies for which SAP will not take responsibility. You should only use the public APIs. If something is safe in CL_WDR_TASK, it will be wrapped in a class named CL_WD_*.
From the online help:
General rule is that classes and interfaces beginning with CL_WD_ or IF_WD_ have been released for application developers.
Classes and interfaces beginning with CL_WDR_ or IF_WDR_ have not been released. These classes are not contained in the package interface and they can change without prior notice. Furthermore, there may be side effects from calling these internal class methods.
There are some exceptions to this rule, for instance, CL_WDR_VIEW_ELEMENT. If you are unsure whether a class or interface has been released, you can define a package usage relationship from your package to the package interface SWDP, and activate server and client checks for your package. The extended syntax check then indicates whether you are allowed to use a certain object or not.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.