It's all about the answers!

Ask a question

Why the repository model has limitation for hierarchy level


Qiong Feng Huang (76911610) | asked Feb 16 '09, 8:24 a.m.
JAZZ DEVELOPER
I heard from some one that the repository model only support no more than 3 hierachy level. For example: we have a model and A is an Auditable and B extends A, C extends B. In this case, no other type could extent C because of the limitation. Is that right? And if so, why the repository model has this kind of limitation?

One answer



permanent link
Matt Lavin (2.7k2) | answered Feb 16 '09, 8:38 a.m.
FORUM MODERATOR / JAZZ DEVELOPER
You are right about the restriction. The reason for the restriction is
that it simplified the implementation of the storage code, and we found
that more than 2 levels was not needed in practice. It is usually
possible to shape the model in a different way to achieve the same
goals.

Additionally, in the Jazz Foundation 1.0 (RTC 2.0) time frame, it is not
recommended to create new server side extensions. A much better
approach for extending a Jazz server is to use the Jazz REST Services
API to store data in the server without having to install code on the
server (or build custom EMF models).

-
Matt Lavin
Jazz Server Team


On Mon, 2009-02-16 at 13:28 +0000, huangqf wrote:
I heard from some one that the repository model only support no more
than 3 hierachy level. For example: we have a model and A is an
Auditable and B extends A, C extends B. In this case, no other type
could extent C because of the limitation. Is that right? And if so,
why the repository model has this kind of limitation?

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.