Issue with library usage with Capella 7.0.1?

Capella
1

Hi all,

I tried to use library with capella 7.0.1 and I had an issue

So I did comparison between V7.0.1 (build id: 202503211540)

and V6.0.0 (build id: 202209090800). In both cases I don’t have any additional addon

At first I created à library “MyLIB”, with a short modeling at logical level

I created à project “MyProj” and associate MyLIB to MyProj (by “Library/Manage reference”)

With Capella 6.0.0 I can drop and paste a Logical component form MyLIB to MyProj.

It’s not working with Capella 7.0.1

Attached document show screen captures comparison.

Could you please help me to resolve this issue?

Note: maybe it’s possible this is similar issue that this one: I can’t use components from a library in my project using capela 7.0 · Issue #2944 · eclipse-capella/capella

Library usage comparison V6.0.0 vs V7.0.1.pdf (897,1 Ko)

2

The issue here is that what is working in Capella 6.0.0 should not be working. This is a bug. Capella 7.0.1 fixed that bug…

Let me elaborate a little bit.

In Capella, there is an important distinction between data elements (Classes, Exchange Items, Data Types, etc.) and architecture elements (Logical Components, Functions, Capabilities, etc.).

When a project references a library:

  • Data elements can be directly reused by reference (for example in type definitions).

  • Architecture elements (such as Logical Components) are not meant to be directly copied or dropped into the project model structure from the library.

For architectural elements, the supported reuse mechanism is based on REC/RPL (Reusable Element / Replica):

  • You define reusable content as a REC in the library.

  • You instantiate it as an RPL in the consuming project.

In Capella 6.0.0, drag & drop of Logical Components from a library may have appeared to work, but this was not the recommended or fully supported reuse mechanism for structural elements. In more recent versions (including 7.0.1), the behavior is stricter and aligned with the intended reuse model.

If your need is to share common architectural building blocks across projects, REC/RPL is the correct mechanism to use in a library.

I hope this clarifies the situation.

Stephane

3

Thank you very much Stéphane for your quick answer. I just used with REC/RPL mechanism associated with library on 7.0.1 version

1 Like