Re: AW: AW: Forgot subject: Strange Could not locate metadata for the classError?

Hans- If I understand it right - above lookup code will ensure that there is only a single EM within a JTA transaction even if I call the method several times from several methods within the TX. Yes, it should. You might want to print out the System.identityHashCode(broker) to be sure,

[jira] Commented: (OPENJPA-176) Exception prefixes should be human-readable

[ https://issues.apache.org/jira/browse/OPENJPA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483852 ] Michael Dick commented on OPENJPA-176: -- It looks like we just use type + error if the type isn't recognized.

[jira] Resolved: (OPENJPA-176) Exception prefixes should be human-readable

[ https://issues.apache.org/jira/browse/OPENJPA-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marc Prud'hommeaux resolved OPENJPA-176. Resolution: Fixed Fix Version/s: 0.9.7 Implemented patch. Exception

Re: Shared classloader and subclasses

Abe White wrote: I see. Here's a proposal: in the MetaDataRepository's implementation of the RegisterClassListener interface, the repository only registers the given class if either the user has not specified a persistent types list (which we allow and in which case we attempt to lazily