Hi, The current OCM require existing Java classes when mapping JCR content to Java objects. This introduces a relatively high entry barrier for various scripting environments, where you just want access to JavaBean properties as name-value pairs without having to set up explicit content mappings.
To make life easier for such environments I'd like to propose implementing a JCR binding for the DynaBean concept [1] in Commons BeanUtils. [1] http://commons.apache.org/beanutils/commons-beanutils-1.7.0/docs/api/org/apache/commons/beanutils/package-summary.html#dynamic BR, Jukka Zitting
