Dear All, Given we have a lot of archetypes which are then further versioned etc moving archetypes from one version to another can become a real pain based on their inherited content.
i.e. if B.v1 specializes A.v1 then it includes the content of A.v1 If we then create an A.v2 & wish to create a B.v2 which specialises A.v2 (or even we have a b.v1draft which we we to change to specializing/extending A.v2) a manual process must ensue so that the content brought in from A.v2 replaces the content brought n from A.v1. I have heard comment that this is changing so that Archetypes become like normal classes i.e. the superclass content does not appear in the subclass & if a given method does appear in the subclass then it overrides that in the superclass. A) Is this so? If not it should be B) If this is so, any ideas wrt dates & tooling etc to support this (inc wrt the java tooling)? TIA Adam ********************************************************************** This message may contain confidential and privileged information. If you are not the intended recipient please accept our apologies. Please do not disclose, copy or distribute information in this e-mail or take any action in reliance on its contents: to do so is strictly prohibited and may be unlawful. Please inform us that this message has gone astray before deleting it. Thank you for your co-operation. NHSmail is used daily by over 100,000 staff in the NHS. Over a million messages are sent every day by the system. To find out why more and more NHS personnel are switching to this NHS Connecting for Health system please visit www.connectingforhealth.nhs.uk/nhsmail **********************************************************************
