Re: An object of type "src.StatusUpdate" with oid "0" already exists in this context; another cannot be persisted.

2010-05-12 Thread Rick Curtis
You're right, it looks like I messed up and sent you the old code. I need to run quickly here, so either you can try to build openjpa yourself tonight, or you can wait for the nightly build and pickup the changes tomorrow. Sorry about the runaround. Thanks, Rick

Re: An object of type "src.StatusUpdate" with oid "0" already exists in this context; another cannot be persisted.

2010-05-12 Thread Midyat
I'm very sorry. I removed openjpa-all-2.0.0.jar from buildpath. I added your sandbox build pttebt.jar to the buildpath. Same result. Thanks for all effort, but it doesn't work. The same issue as originally reported is still there. -- View this message in context: http://openjpa.208410.n2.nabble

Re: NoClassDefFoundError in JavaSE environment

2010-05-12 Thread Laird Nelson
Interestingly, when I crank the logging up, and when OpenJPA is reporting its properties, it says: openjpa.RuntimeUnenhancedClasses: 0 Like I said, I have ...in my persistence.xml. Is something happening here? Thanks, Laird On Wed, May 12, 2010 at 4:00 PM, Laird Nelson wrote:

NoClassDefFoundError in JavaSE environment

2010-05-12 Thread Laird Nelson
I'm getting an odd NoClassDefFoundError while running unit tests in a standard Java SE environment. I'm on Java 6 with OpenJPA 2.0.0-beta3. I have an AbstractType class that is a @MappedSuperclass. It is in one jar file. It contains, among other things, an @Id mapping, and a couple of straightfo

Re: An object of type "src.StatusUpdate" with oid "0" already exists in this context; another cannot be persisted.

2010-05-12 Thread Rick Curtis
I committed a change to trunk. I also posted a sandbox build with the change to filebin[1] if you would like to give that a try. [1]http://filebin.ca/pttebt Thanks, Rick

Re: An object of type "src.StatusUpdate" with oid "0" already exists in this context; another cannot be persisted.

2010-05-12 Thread Rick Curtis
Midyat wrote: > > You can add my code example as attachment to the bug in JIRA. > Because the link on rapidshare will be deleted in a few days. > I'm working on a fixing the problem right now. I should have a change committed later this afternoon. http://issues.apache.org/jira/browse/OPENJPA-

Re: JPA 3.0

2010-05-12 Thread Christopher Gardner
I don't know why it couldn't be a 3rd party item. On Wed, May 12, 2010 at 10:10 AM, Kevin Sutter wrote: > :-) Thanks, Laird. This is the type of processing that I was envisioning > with Christopher's post. Neat, cool idea. But, I'm still looking for the > practicality of the proposal. From

Re: JPA 3.0

2010-05-12 Thread Kevin Sutter
Hi Matthew, I can agree with the idea of dynamically generating classes at runtime and be able to persist them and use them in queries. But, the dynamic generation of mappings makes me go tilt. :-) Kevin On Wed, May 12, 2010 at 9:56 AM, Matthew Adams wrote: > I don't think the intent is to be

Re: JPA 3.0

2010-05-12 Thread Kevin Sutter
Hi Chris, Fairly loaded response... :-) As with any "new" technology, some features of past technologies will still be missing. Some of these features are skipped on purpose (let's see if these are really required), others are still on the plate but couldn't contain in the current release, and o

Re: JPA 3.0

2010-05-12 Thread Matthew Adams
I don't think the intent is to be able to dynamically change mappings, although I suppose that's certainly possible. The primary use case for the metadata API is to be able to generate classes at runtime and be able to persist them. I didn't follow the metadata API justification email thread too

Re: JPA 3.0

2010-05-12 Thread Kevin Sutter
:-) Thanks, Laird. This is the type of processing that I was envisioning with Christopher's post. Neat, cool idea. But, I'm still looking for the practicality of the proposal. From what I am reading on the EclipseLink site, doing something similar in OpenJPA certainly looks doable. I just don

Re: JPA 3.0

2010-05-12 Thread ljnelson
Interestingly, this just came up over in EclipseLink land: http://wiki.eclipse.org/EclipseLink/Examples/JPA/Dynamic Best, Laird On Wed, May 12, 2010 at 9:36 AM, Kevin Sutter [via OpenJPA] < ml-node+504-372614786-210...@n2.nabble.com > wrote: > Hi Christopher, > Hmmm... Interesting idea, bu

Re: JPA 3.0

2010-05-12 Thread Kevin Sutter
Hi Christopher, Hmmm... Interesting idea, but is this dynamic mapping really practical? It sounds like you are looking for the means to dynamically create or change the mappings defined by your Entity and your database Schema. The attribute types in your Entity definitions will need to match (or

Re: An object of type "src.StatusUpdate" with oid "0" already exists in this context; another cannot be persisted.

2010-05-12 Thread Midyat
You can add my code example as attachment to the bug in JIRA. Because the link on rapidshare will be deleted in a few days. -- View this message in context: http://openjpa.208410.n2.nabble.com/An-object-of-type-src-StatusUpdate-with-oid-0-already-exists-in-this-context-another-cannot-be-persi-tp

Re: An object of type "src.StatusUpdate" with oid "0" already exists in this context; another cannot be persisted.

2010-05-12 Thread Midyat
I started already thinking that it was a bug, because the issue looks very weird. Thanks for investigating and confirming that it's a bug. I don't have a JIRA account to report a bug. Maybe you can do it? Can you please let me know how/where I can track the bug? PS: It's very annoying if you