[jira] Updated: (OPENJPA-241) Extra SQL on lazy CMR load

[ https://issues.apache.org/jira/browse/OPENJPA-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Fay Wang updated OPENJPA-241: - Attachment: openjpa_241.patch The attached patch fixes the scenario described by Rob. The following is t

[jira] Created: (OPENJPA-663) Index creation fails when default schema does not exist

Index creation fails when default schema does not exist --- Key: OPENJPA-663 URL: https://issues.apache.org/jira/browse/OPENJPA-663 Project: OpenJPA Issue Type: Bug Components: sq

Re: composite ID w/ another composite ID as a field

Hi, SVN commit 678518 [1] addresses this problem. We have cannibalized your tests also. It will be good if you can verify the changes with latest OpenJPA trunk build that includes 678518 [1] http://svn.apache.org/viewvc?view=rev&revision=678518 -- View this message in context: http://n2.n

[jira] Updated: (OPENJPA-207) failure when composite ID has another composite ID as a field

[ https://issues.apache.org/jira/browse/OPENJPA-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar updated OPENJPA-207: -- Priority: Major (was: Minor) > failure when composite ID has another composite ID as a field

[jira] Commented: (OPENJPA-207) failure when composite ID has another composite ID as a field

[ https://issues.apache.org/jira/browse/OPENJPA-207?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615338#action_12615338 ] Pinaki Poddar commented on OPENJPA-207: --- The change incorporated includes a change i

[jira] Assigned: (OPENJPA-207) failure when composite ID has another composite ID as a field

[ https://issues.apache.org/jira/browse/OPENJPA-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Pinaki Poddar reassigned OPENJPA-207: - Assignee: Pinaki Poddar > failure when composite ID has another composite ID as a field

OpenJPA enhancement in classloader

Hi All, for a number of reasons I cannot explain right now ( :) ), I need to load JPA annotated classes, and enhance them with OpenJPA, from a ClassLoader, and not from an agent or a J2EE environment. I wrote a classloader that calls the PCClassFileTransformer inside the defineClass method, I used

Re: snapshot process (was: Re: Documentation links and content "out of date")

Hi, I gave this a quick test and it looks like it's working, here's exactly what I ran : $ mvn -Dmaven.test.skip=true deploy -DaltDeploymentRepository=myserver::default::scp:// myserver.myhost.com/home/mikedd/temp22 $ mvn -Dmaven.test.skip=true site:stage-deploy -DstagingSiteURL=scp://myserver.m

Re: [VOTE] Approve OpenJPA 1.0.3 release

As I was attempting to verify some of the driver artifacts, I came across an item that confused me. So, maybe it would confuse other readers as well... When looking at the driver, I followed the openjpa"-all" path (note that the "-all" is dropped from our package names when doing a release). In

[jira] Assigned: (OPENJPA-134) Extra unneeded SQL joins for OneToMany relationship with fetch type EAGER

[ https://issues.apache.org/jira/browse/OPENJPA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevin Sutter reassigned OPENJPA-134: Assignee: Fay Wang > Extra unneeded SQL joins for OneToMany relationship with fetch type E