[jira] Commented: (OPENJPA-1899) Evict from L2 of a object causes secondary objects to never be loaded in graph

[ https://issues.apache.org/jira/browse/OPENJPA-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12965010#action_12965010 ] Robert Krier commented on OPENJPA-1899: --- Hi Rick, I have re-uploaded the test case

[jira] Updated: (OPENJPA-1899) Evict from L2 of a object causes secondary objects to never be loaded in graph

[ https://issues.apache.org/jira/browse/OPENJPA-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Krier updated OPENJPA-1899: -- Attachment: evictproblem.zip Uploaded again with proper attachment license. > Evict from L2

Re: AttachStrategy Question

Hi Michael! Txs 4 the quick response! Yea, you got this scenario right, I detach first (in one request), and then I set the entity before doing the merge (JSF postback in the 2nd request). I took care that no serialisation is involved (using CODI @ViewAccessScoped and not the JSF ViewMap), so

Re: AttachStrategy Question

Re-read your original email, and this makes more sense now. I think what's happening is that you're detaching, setting a field to null, and then merging the entity into a persistence context. When you flush to the database the field that you set to null is not saved (any other changed fields would

Re: AttachStrategy Question

Hi Mark, I'm not sure exactly what you're doing to cause the error, a unit test would definitely help there. The openjpa.DetachState property is a way to specify which fields will be present when an entity is detached. Using a different DetachState value may result in different results depending

[jira] Commented: (OPENJPA-1899) Evict from L2 of a object causes secondary objects to never be loaded in graph

[ https://issues.apache.org/jira/browse/OPENJPA-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12964927#action_12964927 ] Rick Curtis commented on OPENJPA-1899: -- ...thanks for the test case but we can't use

Re: OpenJPA 2.1 timeline

Hi all, Doing the formal release should be easy, but I've found that a few gotcha's crop up each time. Usually they're just time consuming though. Unless someone objects I'll go ahead and create a 2.1.x branch and move trunk to 2.2.0-SNAPSHOT so we're at least ready for a formal release. -mike

[FYI] Fw: [mojo-dev] [VOTE] release openjpa-maven-plugin 1.2

Hi folks! I did all necessary steps to stage the last codehaus based openjpa-maven-plugin and called a [VOTE]. After this release, we'd like to contribute the source to the OpenJPA community. Feel free to vote and report back issues ;) txs and LieGrue, strub --- On Mon, 11/29/10, Mark Strub

[jira] Updated: (OPENJPA-1899) Evict from L2 of a object causes secondary objects to never be loaded in graph

[ https://issues.apache.org/jira/browse/OPENJPA-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Krier updated OPENJPA-1899: -- Description: I have a simple example. A customer has a reference to an address and a (prima

[jira] Updated: (OPENJPA-1899) Evict from L2 of a object causes secondary objects to never be loaded in graph

[ https://issues.apache.org/jira/browse/OPENJPA-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Krier updated OPENJPA-1899: -- Attachment: evictproblem.zip Instructions: Unzip the attached file. In the conf directory,

[jira] Created: (OPENJPA-1899) Evict from L2 of a object causes secondary objects to never be loaded in graph

Evict from L2 of a object causes secondary objects to never be loaded in graph -- Key: OPENJPA-1899 URL: https://issues.apache.org/jira/browse/OPENJPA-1899 Project: OpenJPA

[jira] Created: (OPENJPA-1898) TestQueryMultiThreaded fails with OOME "unable to create new native thread"

TestQueryMultiThreaded fails with OOME "unable to create new native thread" --- Key: OPENJPA-1898 URL: https://issues.apache.org/jira/browse/OPENJPA-1898 Project: OpenJPA

Re: OpenJPA 2.1 timeline

Hi Kevin! Since OpenJPA already derives the settings from apache-parent-7 it should not be a big problem to do the actual maven release tasks. If you need some help, I can volunteer on this one. Of course, I have no idea what else needs to be done in OpenJPA on the orga side (but I guess it w

Re: OpenJPA 2.1 timeline

Hi Kevin, Thanks for the update. We'll be glad to help in the process. Regards, Guy Korland On Mon, Nov 29, 2010 at 6:27 PM, Kevin Sutter [via OpenJPA] < ml-node+5784950-672444774-300...@n2.nabble.com > wrote: > Hi Guy, > One of our team members that was organizing the 2.1 roadmap and release

Re: OpenJPA 2.1 timeline

Hi Guy, One of our team members that was organizing the 2.1 roadmap and release had to cut back on his involvement on OpenJPA due to other commitments. We're in the process of finding a replacement "release manager". We should be posting something on this topic in the very near future. Thanks fo

DetachedStageManager misere

Hi folks! I just get grey hairs with the DetachedStateManager my situation: .) with default detach strategy -> error in @PostLoad see OPENJPA-1873 -> error in storing Null Values at em.merge() .) with detach strategy fetch-groups -> ElementCollections don't get stored .) with fgs(Detache