[ https://issues.apache.org/jira/browse/JDO-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924687#action_12924687 ]
Craig L Russell commented on JDO-667: ------------------------------------- Could you write up a technical description of the method suitable for inclusion in the specification, and think about writing test cases? When does a class appear in the list? In JDO, classes and metadata are loaded lazily, so we need to decide when a class is required to be in the list, and when a class is allowed to be in the list. > Extend PersistenceManageFactory to return all known entity classes > ------------------------------------------------------------------ > > Key: JDO-667 > URL: https://issues.apache.org/jira/browse/JDO-667 > Project: JDO > Issue Type: New Feature > Affects Versions: JDO 3 > Reporter: Marco > Fix For: JDO 3 maintenance release 1 > > > JDO 3 now has the ability to declare meta-data programmatically. Part of this > feature is the ability to ask the PersistenceManagerFactory via the method > getMetadata(java.lang.String) for the meta-data of one single class. But > there is no way to list all known classes. > I therefore kindly ask for a new method in PersistenceManagerFactory like > this: > Collection<String> getClassesWithMetadata(); > Btw., this is Andy's suggestion posted here: > http://www.datanucleus.org/servlet/forum/viewthread_thread,6379#33224 > I'd greatly appreciate, if this method became a part of JDO 3.1. > Edit 1: I just saw the various overloaded methods getManagedObjects(...) in > PersistenceManager - maybe the alternative method name "getManagedClasses()" > would be more consistent? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.