Fields defined on an extension can only be private, internal or public but not protected.

(0) Share

Report

Posted on by @rp@n

Hi Team,

I have created an extension class for SalesConfirmDP but got below error while rebuilding.

I guess, it is happening because of final keyword declaration. If yes , than how I can resolve this issue?

Pls give me more shed on this.

thanks!

I have the same question (0)

All responses (8)

Answers (2)

Sort by

Suggested answer

Martin Dráb 239,670 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

What problem do you see there to solve?

Protected members are used with inheritance and you can't inherit from final classes. And there is no point in having anything else than a final class, because the extension class is instantiated by the system (in a very special way) and it would never use a child class if there was any. Therefore it's all as it should be.

Was this reply helpful? Yes No
@rp@n 56 on at

Like (0)

Report
Copy link

Link copied!

Let me know how can I solve this? What changes are required?

Was this reply helpful? Yes No
Martin Dráb 239,670 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

I'm sorry, but I still don't know what you want to solve.

Was this reply helpful? Yes No
Verified answer

GirishS 27,843 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi,

In extension classes if you declare variables globally then you must give access specifier to a variables like below.

Public SalesConfirmDetialsTmp confirmDetailsTmp;

Public int i;

Public int serialization;

Thanks,

Girish S.

Was this reply helpful? Yes No
@rp@n 56 on at

Like (0)

Report
Copy link

Link copied!

Thanks Girish,

Is it always public access modifier to declare in extension class?

Pls give me more shed on this

Was this reply helpful? Yes No
Verified answer

GirishS 27,843 Moderator on at

Like (0)

Report
Copy link

Link copied!

It depends on your requirement. Mostly it will be public only. If you declare it as public it will be accessible in all the methods.

Thanks,

Girish S.

Was this reply helpful? Yes No
@rp@n 56 on at

Like (0)

Report
Copy link

Link copied!

Thanks Girish

Was this reply helpful? Yes No
Martin Dráb 239,670 Most Valuable Professional on at

Like (0)

Report
Copy link

Link copied!

The general recommendation is never using public instance variables. Such a design allows other classes to take dependency on implementation details of your class and it may harm maintainability and extensibility a lot.

Instead, expose the value through a public method. Then you can change the implementation (e.g. change the value how you store the data or add extra logic, such as raising an event on value change) without changing the public interface of the class.

Was this reply helpful? Yes No