Hi Sascha,
This is not possible. The view designer does not support everything that is supported by ABAP OO (like static methods or attributes, constant values, catching any event of any class, etc). Main reasons are that either a certain feature does not fit into WD (static methods) or violates the holy grail of platform independence of WD in ABAP and Java. In WDJ you won't be able to define two methods that have the same name (although the Java language would support it in contrast to ABAP).
Anyways, there have been small expections to this rule in order to adopt WD better to a specific platform. Nonetheless, it would be strange to completely rebuild the ABAP class builder for the purpose of enabling all kinds of ABAP OO language features within the Web Dynrpo design time. Of course, it is obvious that every developer wants to use exceptions, optional parameters, constant values, etc. Hence the assistance class concept was introduced. It doesn't mean that we won't add optional parameters, exceptions or refactoring in future. It means that the assistance class is the (already existing) place to unleash the full power of ABAP OO and all the powerful features that come along with using the class builder such as the refactoring framework and much, much more. The assistance class allows for an easy and convinient integration of ABAP OO into the WDA environment and it's highly advised to use it.
Best regards,
Thomas
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.