archetype in memory creation

Implementers (archive)
1

Hi, I wonder about this,

If one creates an Arcehtype in Memory, and writes it out to an ADL-file. (This possible in the Java-implementation using ADLOutputter),
and then read it back, into memory, if one has the same Archetype in memory?

I have this in memory

org.openehr.am.archetype.constraintmodel.CComplexObject@178aae1
[
attributes=[org.openehr.am.archetype.constraintmodel.CMultipleAttribute@45378f
[
cardinality=org.openehr.am.archetype.constraintmodel.Cardinality@2f1e75
logger=org.apache.log4j.Logger@15b0e2c
rmAttributeName=value
existence=REQUIRED
children=
org.openehr.am.archetype.constraintmodel.ArchetypeSlot@5e7020
[
includes=
[
REPC_MT000001NL.Performer2
]
excludes=<null>
rmTypeName=performer
occurrences=org.openehr.rm.support.basic.Interval@58e2a1
[
lower=1,lowerInclusive=true,upper=1,upperInclusive=true
]
nodeID=at10076
anyAllowed=false
path=/[at00001]/Content[at10001]/items[at10076]/
]
invariants=<null>
logger=org.apache.log4j.Logger@848ecc
rmTypeName=ELEMENT
occurrences=<null>
nodeID=at10075
anyAllowed=false
path=/[at00001]/Content[at10001]/items[at10075]/
]
]

When I write this to ADL, using ADLOutputter, I get this:

ELEMENT[at10075] matches {
value cardinality matches {1..1; unordered} matches {
}
}

And when I read this adl-file in memory again, I get this

org.openehr.am.archetype.constraintmodel.CComplexObject@6833f2
[
attributes=
[
org.openehr.am.archetype.constraintmodel.CMultipleAttribute@12a73d9
[
cardinality=org.openehr.am.archetype.constraintmodel.Cardinality@1568654
logger=org.apache.log4j.Logger@9aba32
rmAttributeName=value
existence=REQUIRED
children=[]
anyAllowed=false
path=/[at00001]/content[at10001]/items[at10075]/.value
]
]
invariants=<null>
logger=org.apache.log4j.Logger@1e152f4
rmTypeName=ELEMENT
occurrences=<null>
nodeID=at10075
anyAllowed=false
path=/[at00001]/content[at10001]/items[at10075]/
]

I am still using 0.95, for the coming weeks I will be using that.

It seems to me that it is erroneous, or do I make an error?
Has this behaviour changed in latter versions (1.0.1)?

Do not pay attention to the “includes”-lines, the contents is not important

Thanks
Bert

2

Hi Bert,

It seems to be a bug. The ADL-AOM round trip for ArchetypeSlot has not been used very much since the RM object creation through archetype slot is not supported currently. It will be implemented soon on the latest version. Try to avoid using archetype slot with your current project and use it with later version of the java implementation when it's supported.

Regards,
Rong

Bert Verhees wrote:

3

Rong Chen schreef:

Hi Bert,

It seems to be a bug. The ADL-AOM round trip for ArchetypeSlot has not
been used very much since the RM object creation through archetype slot
is not supported currently. It will be implemented soon on the latest
version. Try to avoid using archetype slot with your current project and
use it with later version of the java implementation when it's supported.

Oeps....

This is Dutch for "Oops"

regards
Bert