[ https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12652846#action_12652846 ]
Andy Jefferson commented on JDO-615: ------------------------------------ If you create JDOMetaData via a services entry and there are more than 1 possible in the CLASSPATH how does JDOHelper know that it is picking the right one that is compatible with the JDO implementation that will be used? e.g an app using JDO impl 1 for legacy module 1, and JDO impl 2 for new module 2. While all implementations of XXXMetadata will implement it, it is reasonable for a JDO implementation to only accept its own implementation of the XXXMetadata interfaces to be registered. Regarding spelling : No comment (to be made by me on American spellings ;-) ) > MetaData specification API > -------------------------- > > Key: JDO-615 > URL: https://issues.apache.org/jira/browse/JDO-615 > Project: JDO > Issue Type: New Feature > Reporter: Andy Jefferson > Fix For: JDO 2 maintenance release 3 > > Attachments: jdometadata-4.patch > > > We can specify MetaData via XML or annotations. The only way missing is via > an API. I propose mirroring the XML structure with interfaces of the form > public interface MetaData > { > addExtension(String key, String value); > removeExtension(String key, String value); > ... > } > public interface FileMetaData > { > addPackage(PackageMetaData pmd); > ... > } > public interface PackageMetaData > { > addClass(ClassMetaData cmd) > ... > } > public interface ClassMetaData > { > addField(FieldMetaData fmd) > ... > } > public interface FieldMetaData > { > setInheritance(InheritanceMetaData inhmd) > ... > } > and so on. > We would then require a method on the PMF to register the metadata. > If there are no objections to such a feature I'll propose a patch to try to > provide all current JDO2 capabilities. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.