Wonderland nested access

[Felix Mayerhuber]

Hi,

I've added a new way to access nested models inside a model from
Wonderland transformation descriptions (see
http://issues.openengsb.org/jira/browse/OPENENGSB-3455). This opens a
possibility so simplify some transformations.

However, this also opens a different topic: What if a property has the
type of a list of models? To support them fully, we need two ways to
access them:
- by id, for example nested.1.value1
- access them all, for example nested.forAll.value1, which returns a
set of objects

The issue for that is already created:
http://issues.openengsb.org/jira/browse/OPENENGSB-3462

Are there any already known use-cases for this type of property access?

Kind regards,
Felix

[Florian Waltersdorfer]

Hi,
tried to guess whether some of "my" scenarios would make use of this:
- for a 2-layered map-lookup (i.e. "the first map contains references to other maps), I think we will not need this
- for data structures that resemble topologies, this could

regards flo
--
Sent from my mobile, please excuse my brevity.

[Florian Waltersdorfer]

... be very useful (i.e. "I have some top-level-components containing 2 or 3 layers of nested models in one domain and need to flatten this or transform to a completely different topology"), but I don't know all the details here (MPe and MSei might know better)

regards^2 flo

PS: sry, got bumped and hit the send button

--
Sent from my mobile, please excuse my brevity.

[Kristof Meixner]

Hi!

One known UC. At SMS we need a way to build up a hierarchical structure of models (see below).

Best regards,
Kristof

PC
|-Strand01
| |-ECoppler00
| | |-EClamp00
| | `-EClamp01
| `-ECoppler01
| |-EClamp02
| `-EClamp03
`-Strand02

[Felix Mayerhuber]

Good to know. Then I can add them to the description of the issue.

Kind regards
Felix