cancel
Showing results for 
Search instead for 
Did you mean: 

Basic Doubts

Former Member
0 Kudos

Hi,

I have some basic doubts about WDP. Can someone please clarify.

<b>Statement</b> : "The metadata of the WDP applications is independent of the platform on which the application is executed. It is therefore possible to transport the application to a platform after implementing it on another. The metadata is transported to the platform-specific development environment; the source code required for this platform is generated. Only the source code that you have programmed for the event handling,for eg, would have to adopted to suit the new platform."

<b>Doubt</b> : Supposte that we implement a WDP application in NWDS and I want some ABAP guy to make changes to it. What should I do ? Do I need to simply give the project developed in NWDS to that guy so that he can open it in ABAP workbench and work on it ? And what happens to the custom code (for eg event handling code) that I wrote in the NWDS, will that still stay or that guy has to rewrite it again ? 2) What should be done to run this application developed in NWDS to run in an ABAP or .Net environment ?

Can someone explain this platform indepence feature in detail ?

<b>2nd Doubt</b> :

What does one mean when they say one of the advantages of WDP is "Configuration of UI Patterns"

What does one mean when they say one of the advantages of WDP is "browser based, <b>zero footprint</b> "

What does one mean when they say one of the advantages of WDP is "screen updates <b>without page reloads</b> "

What does one mean when they say one of the advantages of WDP is "508 accessibility support":

What does one mean when they say one of the advantages of WDP is "flicker free screen, <b>minimal refreshs</b> "

What does one mean when they say one of the advantages of WDP is "Client side Dynamics "

Regards,

Fanatic

Accepted Solutions (0)

Answers (1)

Answers (1)

venkatakalyan_karanam
Active Contributor
0 Kudos

Hi Fanatic

1 st Doubt :

you are giving the application to ABAPer,if your application is consisting with RFC models which are used.An abaper can only changes to the RFC Modules in the backend R/3 system.He does not touch the webdynpro code becuase he dont know java programming.At most he is able to change RFC structure.So as a webdynpro developer he knows where the changes has to be taken place regarding the model importing and respective parameters.He does not require the entire application,he needs R3 system where models are created.

2 nd Doubt:

-


Configuration of UI patterns means as per my knowledge

you can change the usage according to your requirements in the design stage.

Declarative approach.

3 rd Doubt

-


I dont have an idea reg this

4 th one

-


Each time the view is rendered the wdModify method will be called of corresponding View Controller.

The entire page is not reloaded in this case

5 th Doubt

-


Client side dynamics means you can do dynamic programming in the View Controller.The View Controller is having full control on the Scn

For more info

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c8780... [original link is broken]

https://www.sdn.sap.com/irj/sdn/developerareas/webdynpro

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/webcontent/uuid/28113de9-0601-0010-71a3-c8780... [original link is broken]

http://help.sap.com/saphelp_nw04/helpdata/en/5c/1b76bc3da0504e8b535cf3e154eaa7/content.htm

/thread/396968 [original link is broken]

regards

kalyan