Re: Problem trying to persist an entity into Derby from a Web App deployed to Geronimo

2007-04-13 Thread Abe White
It sounds like you're never starting or committing a transaction. You're persisting outside of a transaction, which just means that the object will be cached until the next transaction, waiting for a flush/ commit to be inserted into the database.

Re: Problem trying to persist an entity into Derby from a Web App deployed to Geronimo

2007-04-13 Thread Jay D. McHugh
Thanks Abe. Yeah, I figured that out (that I needed a transaction to get it to post). But I then I was having problems creating a transaction within Geronimo. I ended up having to change my persistence unit from being a 'JTA' transaction type to being a 'RESOURCE_LOCAL'. Thanks, Jay Abe

Re: Problem trying to persist an entity into Derby from a Web App deployed to Geronimo

2007-04-12 Thread Jay D. McHugh
Hello again. On further searching, I have found that every field in the meta data is flagged as not being cascade_immediate. So, during the cascadePersist call, nothing is getting single persisted. Was I supposed to do something to get these set to 'cascade_immediate' or is there supposed