How to access attribute inside a method

[Former Member]

Hi,

I have defined an attribute under Attribute tab of Component controller. How to access this inside WDDOINIT of component controller or inside any custom method of any of my view.

Rgds

Sudhanshu

[Former Member · Accepted solution]

For Comp controller:

WD_THIS->ATTR

For View:

WD_COMP_CONTROLLER->ATTR

[bjorn-henrik_zink]

Hi sudhanshu sharma,

please search the forum before posting your question, I believe there are many answers to your question out there.

Anyway, here you have an example of how to access a context attribute from within your component controller:

wd_this->attribute_name.

Hope it helps

[Former Member]

For accessing the attribute from view also check that the attribute visibility is marked as PUBLIC

[bjorn-henrik_zink]

From a design point of view I would adwise not to directly access the component controller attributes. Instead, use set and get methods for accessing the attributes.

[Former Member]

Hi,

Can you please let me know pros and cons of direct accessing of component controller attribute.

Rgds

Sudhanshu

[Former Member]

Hi Sudhanshu,

You can directly access the context attribute by set and get methods.

[bjorn-henrik_zink]

Hi,

I was thinking about the advantages of encapsulation. In my last post, I forgot to mention that this applies for the scenario where you get the attribute value from your view.

It seems that you have some data in your component controller which you want to access in the view. Perhaps you should consider using context binding instead of attributes?

/Björn-Henrik

[Former Member]

Hi,

You made a good point however my requirement doesn't make any impact on design. All i wanted was a boolean flag to check whether my itab is initial or not and then need to perform some action in diffrent methods of same view. Im currently using component attribute and it is fine for me now. Thank you so much Sanket, Elvez and all bloggers.

Rgds

Sudhanshu

[thomas_jung]

>It seems that you have some data in your component controller which you want to access in the view. Perhaps you should consider using context binding instead of attributes?

Why suggest that you should use the context instead? The context should only be used if you need to data bind into the UI elements. Otherwise it is advisable from a performance standpoint to not use the context. The context comes with a considerable memory and processing overhead. Never use the context unless absolutely necessary for data binding. Otherwise use attributes of the controllers themselves or use some external class (like the assistance class) to hold such data.

[bjorn-henrik_zink]

Hi Thomas,

I fully agree with you. In my previous post I did not recommend using a context attribute for all cases (I did use the word "perhaps"). However, if it is bound to a UI element and used acrossed various views, I would probably go for a context attribute. This is not the case in this thread and therefore a context attribute should not be used.

/Björn-Henrik