Vous êtes sur la page 1sur 1

When I click to create a roundtrip to the server and quickly click several times in succession, the

system creates yet another request, which triggers a short dump. If I click slowly or only once, no
short dump occurs.
Answer: Before the system sends the page to the server, it activates a click protection. However, it
takes several milliseconds to activate this protection. During this period the problem described above
may occur. We cannot provide a solution for this problem. The browser environment requires a certain
period to activate the click protection. The protection is executed on the client at the beginning of the
submit handling.

Where can I find further information about Web Dynpro ABAP?


Answer: The following resources are available on SDN (SAP Developer Network):

Forum:
http://forums.sdn.sap.com/forum.jspa?forumID=249
Areas:
https//www.sdn.sap.com/irj/sdn/developerareas/webdynpro
https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro?rid=/webcontent/uuid/512040e1-0901-
0010-769c-c238c6ca35d9
Documentation:

http://help.sap.com/saphelp_nw2004s/helpdata/en/7c/3545415ea6f523e10000000a155106/frameset.ht
m

Do blogs exist that provide information about Web Dynpro ABAP?


Answer: Yes. Information is available on SDN at: http://www.sdn.sap.com/irj/sdn/weblogs?
blog=/weblogs/topic/43

As of which release is Web Dynpro ABAP available?


Answer: Web Dynpro ABAP is available as of NetWeaver 2004s (7.00).

I have installed Basis Release 6.40, and this release contains development objects of Web Dynpro
ABAP. Do I have the option to use Web Dynpro ABAP on this release?
Answer: Web Dynpro ABAP is not released for Release 6.40. For more information, see Note 751611.

After I implement Note 986790 to solve shared memory problems, JavaScript errors occur when
I execute Web Dynpro applications.
Answer: Deimplement Note 986790. Implementing this note causes the problems described.

With complex screens, the application suddenly stops working correctly. What could be the
cause?
Answer: If UI container elements are nested in Web Dynpro views (for example, five tabs within each
other), it leads to very high nesting depths of the HTML rendering tag. As of a depth of approximately
100, the browser stalls, because it cannot process such deep hierarchies. The solution is to simplify the
views by decreasing the nesting depth. Web Dynpro does not provide for a generic simplification.

Where can I find a list of limitations for Web Dynpro ABAP?Answer: Note 1098009 describes the
limitations that currently apply.

Vous aimerez peut-être aussi