Merging projects

[Former Member]

Hi all,

I have a question about merging projects. If several developers are working on the same project and want to combine everything into one project for deployment, can this be achieved? Some developers are also working on the same component but on different aspects of it, can we merge the same component?

[Former Member · Accepted solution]

hi tony

regarding developing the different aspects of a single component separately you can use component usage where you define the use of different components in a parent component and use it.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/webdynpro/tu... on server-side eventing - 14.htm

regarding developing a single project as group of applications and navigating between them the following link may be helpful.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/webdynpro/tu... on inter-application-navigation - 15.htm

to develop your project as development components and reusing them the following link gives you a general overview.

http://help.sap.com/saphelp_nw04/helpdata/en/8d/0c3736db115f4b8ce3fc716e3a386c/frameset.htm

regards saravana

[BeGanz]

Hallo Tony,

to develop large-scale Web Dynpro applications in team you can utilize the SAP NetWeaver Development Infrastrucutre. In this case Web Dynpro projects are represented as Web Dynpro Development Components. The great advantage of this approach is based on the fact, that you can design component-based Web Dynpro applications with a clear separation of concerns. Within one single Web Dynpro component (not Development Component) only one single developer should work so that no merging of concurrent versions have to be done.

Have a look at this SAP NetWeaver Online Help Document on <a href="http://help.sap.com/saphelp_nw04/helpdata/en/ae/1ae58540ea454db1aa14fd635bc10d/frameset.htm">Development in a Team</a>.

I'm currently working on new documents and resources describing the component-based Web Dynpro application design. They will be published soon on SDN ... here they are: <a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/bd0e0401-0801-0010-aaab-d0e">Learn How to Design Component Based Web Dynpro Applications</a>

Regards, Bertram

Message was edited by: Bertram Ganz

Added link to sample description page on "Designing Component-based Web Dynpro Applications (38)"

[arun_srinivasan]

hi tony,

The project may have more than one application. In the application we can have more component. The several component in the application can interact using interface controller.

let u consider two component comp1(parent) and comp2(child).u can use interface controller in child for component interaction.

if more than one developer working in single component. consider u developing one view and another person another. u can use that view in ur component.

hope this helps u,

Regards,

Arun.

[vijayakhanna_raman]

Hi Tony,

We can Use the Different Components

inside the applications by means of the

used components in webdynpro Components

can use other components in a well-defined

and controlled manner, can encapsulate

child components, and can publish their

functions in a set of public interfaces

called public parts. These features are

applied in the component model.

Interface controllers is used to

get the data between different components.

Navigation of applications can be done

By means of exit plugs and passing url parameters.

Chect this link also.

Server side eventing:https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/webdynpro/tutorial on server-side eventing - 14.htm

Navigating application:https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/webdynpro/tutorial on inter-application-navigation - 15.htm

Regards,

Vijayakhanna Raman