[ https://issues.apache.org/jira/browse/JDO-615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714310#action_12714310 ]
Matthew T. Adams commented on JDO-615: -------------------------------------- So it looks like the patch program has difficulty with patch files created via 'svn diff ...' that include a renamed file. I'd prefer that DataNucleus make the change when they're ready and then commit rather than bother with svn diff with renamed files (plus my 1.6/1.5 working copy version issues). > MetaData specification API > -------------------------- > > Key: JDO-615 > URL: https://issues.apache.org/jira/browse/JDO-615 > Project: JDO > Issue Type: New Feature > Components: api2, specification, tck2 > Reporter: Andy Jefferson > Assignee: Craig Russell > Fix For: JDO 2 maintenance release 3 > > Attachments: BooleanProperties.patch, jdometadata-6.patch, > type-2.patch, type.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.