Skip to Content
avatar image
Former Member

Model DC or Model Component ???

Hi all,

In a track we have to create 15 web dynpro DCs. Each of these dcs have got multiple applications and components in them. But none of the models are used by more than one dc.

So, should we go for:

a seperate model dc


a component in every DC exclusively for the models used in that DC and reuse it in the different components in it?

Which option should we follow?

Thanks in advance,


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Apr 30, 2007 at 12:04 PM


    If you are sure that , no two DCs will use a single model at anytime down the line, then there is <b>no point in creating separate model DC</b>. Since DCs are used to distribute the dependancies, and your project does not have any dependancy, so no need to create separate model DC for each WD DC.

    Also, as Models stand out of component , i.e. they are not component dependant, it is of <b>no meaning to create separate component for them</b>. It will simply increase your overhead and stress in managing all the component.

    Model stands out of component (Component comprises only window, custom controller,component controller, views, interface view). So a Model defined in a project as its scope across the project and hence can be used in any component by making their entry in <b>Used Model</b>.

    So , keep your project structure simple by not going to either of them, and just create a model for each project , you can make their use explicit by using them under "Used Models" of as many component as you want.

    hope it helps


    Add comment
    10|10000 characters needed characters exceeded