structure of webdynpro

[Former Member]

hi experts,

we are implementing ep with webdynpro for our project, what my ? is, is there any stucture to follow at the time of develoment for webdynpro (for example developing uielements,coding standards, coding,transporting objects etc...)

if anybodyhelp me on this issue,guide me how we can proceed

with regards,

vijay

[Former Member]

Hai,

<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/9f/656442a1c4de54e10000000a155106/frameset.htm">Webdynpro UI elements</a>

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/011ccf90-0201-0010-92a7-b319adf89b73">Coding Conventions</a><a href=",http://">,http://</a>

Regards,

Naga

[former_member189631]

Hi Vijay,

This is the Link,

http://help.sap.com/saphelp_nw04/helpdata/en/19/8bf3948518984d9381026009600a34/frameset.htm

Regards,

<b>Ramganesan K</b>

[abhijeet_mukkawar]

Vijay,

There is no such 'must follow' coding or UI design standard in WD, but for coding there are some recommendation to be followed: Visit this link, a tutorial is covered which will guide you through some UI design recommendation.

https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/5c8500cd-0401-0010-d49e-af15579891a7

Regarding coding, it depends on the standard defined to you by your client. Just follow that and for UI design take a look at above application.

regards

[Former Member]

hi abhijeet,

i cant open the link which is given by u in the past post today (i.e) https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/library/uuid/5c8500cd-0401-0010-d49e-af15579891a7

with regards

Vijay

[abhijeet_mukkawar]

Vijay,

there seems some problem in that link, can you do one thing , give me your email ID, i will forward the docs to you.

regards

[Former Member]

hi abhijeet,

u can send to this email id vijayaprakash_gopu@yahoo.co.in

thank u

Vijay

[abhijeet_mukkawar]

email has been sent to you.

regards

reward points if that is useful

[Former Member]

Hi,

If you intend to have multiple users to develop the application, i suggest you create a track on your DTR, and use that track for development.

Create activities on the track so that the changes that each developer will make, get added to the DTR in an errorfree manner.

Create seperate activities for your JDTs, EJBs, EARs and Dynpro

If you are going to have EJBs and Java dictionary tables in your project, build and deploy the dictionary first, then the ejb and then finally the EAR(which u need to encapsulate your EJBs).

Finally, create your dynpro applicaiton, with the views, windows, etc

If u intend to consume your ejbs as a webservice, u need to first expose your ejbs as webservices. Then conusme them in your Dynpro Application as Models, and then create the appropriate context mappings.

If u are using EJBs and JDTs, then have all your business logic in the EJBs and use the dynpro as a mere UI front end. The dynpro part can act as the decision makers, but have the resulting actions in your ejbs.

As far as coding goes, follow some basic coding standards & naming conventions, as it becomes easier for the next developer to comprehend the code.

Finally checkin your activities in the following order: JDT, EJB,EAR,dynpro

I hope this information will atlest point you in the right direction.

Regards,

hanoz

[Former Member]

hi hanoz ,

thank u for reply, we are not using ejbs we are using only webdynpro

with regards

vijay

[Former Member]

hi hanoz,

i have a query about application. is it possible to keep all my views or forms in a single application that is to develop all forms in a single project .

if not how we can integrate the diffrent applications(projects) as one in webdynpro.

with warm regards,

vijay

[Former Member]

Hai,

You can use number of views in one Webdynpro Application, but using Componenst You can get the benefit of re-usablity.

See for Details

https://www.sdn.sap.com/irj/sdn/webdynpro?rid=/library/uuid/601b2e6d-be83-2910-d8ba-fe1b594d987e

this blog also

/people/chris.whealy/blog/2006/01/13/when-creating-a-java-web-dynpro-application-dont-use-the-project-type-quotweb-dynpro-projectquot

Regards,

Naga

[Former Member]

Hi vijay,

Yes, it is possible to achieve both!!

u can surely have all your views in a single webdynpo application and project. Its the easiest, but makes the project bulky.

You can even have multiple applications within a single project(however its not a good programming pracitce)

As for having multiple projects, its a good programming practice and it kindof modularises your projects.

Suppose you have a two dypro projectsL A & B.

Expose the <i>public part</i> of B.

Then create a dependancy between A & B by consuming that public part in the <i>used DCs</i> of A.

Then use the Interfaceview(its present in the component controller - component interface) to link the two projects using code logic in the component controller.

your interface view is like a window for your project to communicate with other external projects

I know its a bit confusing, so do let me knw if you need any further clarification

Regards,

Hanoz

[Former Member]

Hi,

I forgot to mention:

If your projects are indepedant, and all you want to do is navigate from one project to another, then you can simply provide URL UI elements, and in their OnAction, provide the URL of the applicaiton(of the project) you want to naviagate to.

But you will need to put proper logic so as to not hardcode the URL, otherwise it will not work once you transport your projects from the application server to the production server.

Regards,

Hanoz

[Former Member]

hi hanoz,

thank u very much for u r help , let me know how we expose the public part of B.

How we create a dependancy between A & B by consuming that public part in the used DCs of A.

How we use the Interfaceview(its present in the component controller - component interface) to link the two projects using code logic in the component controller.

Waiting for replay.

Regards,

Vijai.

[abhijeet_mukkawar]

Vijay,

Lets say u want to use method1() of Comp1 in Comp2.

1. The method should be defined in the interface controller of comp1

2. create a public part in comp1

3. Add the public part in comp2 through Used DC node(In DC metadata, DC definition)

4. Add the comp1 in Used webdynpro components of Comp2

5. Now u can use all the methods of comp1 in comp2 whichever is availablei in interface controller

6. To use u can write following kind code(here in comp2 you goto to the component controller->properties->in required controller add Comp1 as required)

wdThis.wdGet<Comp1>Interface().method1();

Regards

[Former Member]

<b>to create a public part:</b>

1. goto your WebDynpro Explorer view

2. <your project name> -- DC MetaData -- Public parts

3. Right click on Public parts,--New public part

4. provide a name to it, select SDA if you want to create a deployable public part(usually done for JDTs), else use API

5. Click next and select WebDynpro component as the entity type, then select your controller(controller of B in our example)

6. Now build and deploy B

<b>to create dependancies between A & B</b>

When you consume the public part of B in the <i>Used DCs</i> of A, you are making project A dependant on B. However dont make cyclic dependancies by then making B dependant on A.

<b>To consume public part of B in A</b>

1. goto your project A - DC MetaData -- DC Defination -- Used DC

2. Rightclick on Used DC--Add Used DC

3. Search for project B(in the inactive workspace, but make sure you are logged on to the DTR), Used DC--entities.

4. Click on entities, OK

Regards,

Hanoz

[Former Member]

Hi,

When you consume the public parts, you can then use the methods created in project B, in project A.

btw, i forgot to mention, do confirm whether the public part got created in B successfully by expanding the list of public parts of , and the consumption of the same in project A, by expanding the list of Used DCs in prject A.

But let me warn you about this technique of using dependancies between projects.

It is generally observed that creating such multiple projects and then creating dependancies between them, causes problems when another user tries to import the project from the DTR in the future. You need to be very careful when you create activites for the projects and the order with which you checkin them into the DTR.

Creating a single project is always a simpler option.

I hope i have pointed you in the right direction.

Regards,

Hanoz

PS: I dont intend to sound greedy, but if you find the answers useful/insightful, can you please reward points for the same?

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement&

[former_member720137]

Hi Vijay

Web Dynpro is based on MVC Concept i.e Model View Controller Concept.. For more info abt MVC n Web Dynpro..

Go thro Ths links...

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a048387a-0901-0010-13ac-87f9eb649381">MVC</a>

<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/7169a8e5-0601-0010-6d92-90c2aa109568">Web Dynpro Concepts</a>

Do reward points if helpful

Thanks

Puneet