on 07-17-2006 10:38 AM
Hi all,
unfortunately, it occurs again and again that internal classes and interfaces are used and shortly afterwards, problems turn up, apparently out of the blue...
Therefore, this post acts as a friendly reminder that classes and interfaces beginning with
CL_WDR_
or
IF_WDR_
have <b>not</b> 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 a few exceptions though, like CL_WDR_VIEW_ELEMENT. If you are uncertain, define a package usage relationship from your package to package interface SWDP and enable server and client checks on your package. The extended syntax check will tell you, if you are allowed to use a certain object.
There is another thing, I would like to remind you on. Please use constants whereever available. You can either find them at the interface on which you perform a method call or inside of the documentation. Please never, ever use domain values directly. In case you don't find a constant for a particular purpose, don't hesitate to ask your fellow developers in SDN.
Regards, Heidi
Hi Web Dynpro Java Developers,
what Heidi pointed out regarding Web Dynpro ABAP also applies to the Web Dynpro Foundation for Java. Read the particular details on this issue within my WebLog
<a href="/people/bertram.ganz/blog/2005/02/02/never-ever-hijack-internal-web-dynpro-classes-and-interfaces">Never Ever Hijack Internal Web Dynpro Classes and Interfaces</a>.
Regards, Bertram
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.