[
https://issues.apache.org/jira/browse/JDO-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924700#action_12924700
]
Marco commented on JDO-667:
---------------------------
Hi Craig,
thanks a lot for your very quick response! Unfortunately, I can't promise. I'm
currently very busy with a customer's project. If the project ends as planned,
I'll have the first December week time for writing the technical description.
But if the project becomes delayed, I can't say for sure, yet, and I'll be in
holidays afterwards (till the end of January).
Concerning the appearance of the class, I'd say it should be in the list as
soon as the JDO implementation initialises its meta-data. This means normally
when getExtent(...), newQuery(...), makePersistent(...) or sth. similar is
called the first time.
Additionally, if the implementation remembers all previously managed classes
like DataNucleus can
<http://www.datanucleus.org/products/accessplatform_2_2/jdo/autostart.html>,
the classes should be enlisted directly at start-up.
This behaviour is IMHO quite straight-forward and probably what DataNucleus
already does internally.
> 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.
