Skip to Content
author's profile photo
Former Member

Collaboration and Projects

Posted on Nov 20, 2003 at 11:22 AM 10 Views

Hello,

is there a standard way to collaborate using Web Dynpro Projects?

For example, several Components inplement a certain Component Interface (that can not be used outside my project, right?) and are developed by different members of a team.

Can the project (files) be shared and edited simultaneously?

What if the team is small enough to arrange that each Item of the Project is modified by one.

Or is one Project strictly thought to be opened once for modifying? What exactly can be shared between projects (I think of the Jaav Build Path>Projects entries)?

Thanks in advance,

Florian Rehfeld

UI Web Dynpro Java
Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • author's profile photo
    Former Member
    Posted on Nov 25, 2003 at 10:41 AM

    Hello Florian,

    The standard way to collaborate using Web Dynpro projects is by development components (DC).

    Each DC would e.g. implement a Web Dynpro Component and each developer would build

    one component. This DC split-up is available and supported from SP3 upwards.

    In future there will be a development infrastructure (called Designtime Repository) with versioning and code save which knows about the Web Dynpro structure and the DC dependencies.

    This makes collaborative work much more convenient.

    Best regards,

    Karin

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member
      Dec 08, 2003 at 05:00 PM

      Hello Florian,

      a DC can have a public part. A component interface can be part of a public part. DCs can include others. Each DC has exactly one type (e.g. Web Dynpro or Dictionary).

      In order to embed other components at runtime you can define a ComponentUsage

      in the embedding component. This Usage is a relational link on the component which implements the functionality at runtime. The relational link can also refer to a Component Interface / Implementation contained in a public part.

      If I understand your component model below correctly the answer is yes. If the ComponentUsage refers to a Component Interface you can (and have to) specifiy the Component implementation to use during runtime.

      Best regards,

      Karin