# release tag for 1.0.1 **Category:** [Reference Implementation: Java (archive)](https://discourse.openehr.org/c/reference-implementation-java-archive/154) **Created:** 2008-06-29 16:02 UTC **Views:** 2 **Replies:** 2 **URL:** https://discourse.openehr.org/t/release-tag-for-1-0-1/12810 --- ## Post #1 by @system Dear all, I intend to create a release tag for release-1.0.1, which is really a read-only copy of the current Trunk. Compared with the Branch release-1.0.1-RC (release candidate), the current Trunk has been improved considerably. I think the time is right to declare Release-1.0.1 and move on to other tasks, e.g. this would allow us to start to implement the CRs aimed for Release-1.0.2 on the Trunk. Any reaction to this? Cheers, Rong --- ## Post #2 by @system Hi Rong, sorry for the delay...yes I think that is a good idea. There is one thing, in Archetype.java the two methods * Find input name by node path --- ## Post #3 by @system > Hi Rong, > > sorry for the delay...yes I think that is a good idea. > > There is one thing, in Archetype.java > > the two methods > > * Find input name by node path > * > * @param path > * @return null if path unknown > */ > public String inputByPath(String path) { > return pathInputMap.get(path); > } > > /** > * Find node path by input name > * > * @param input > * @return null if input unknown > */ > public String pathByInput(String input) { > return inputPathMap.get(input); > } > > will always return null - as the code that fills the maps (loadInternalRefs()) is in comments. > Is there a problem with this or why was it turned off? Hi Sebastian, These are the relics of the archetype based object creation/validation support in the AOM. The current plan is to separate the logic for validation/creation from AOM, so there is no need to have these methods. I will remove them from the Archetype class. Cheers, Rong --- **Canonical:** https://discourse.openehr.org/t/release-tag-for-1-0-1/12810 **Original content:** https://discourse.openehr.org/t/release-tag-for-1-0-1/12810