Re: Cascade persist and merge with Repository.

2015-07-10 Thread Daniel Cunha
You're welcome. :) On Fri, Jul 10, 2015 at 4:18 PM, akm wrote: > Thanks for all the help you have provided, appreciate it a lot. > > > > -- > View this message in context: > http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002p4

Re: Cascade persist and merge with Repository.

2015-07-10 Thread akm
Thanks for all the help you have provided, appreciate it a lot. -- View this message in context: http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002p4661045.html Sent from the Apache DeltaSpike Incubator Discussions mailing li

Re: Cascade persist and merge with Repository.

2015-07-10 Thread Daniel Cunha
Akm, CdiTestRunner could be some catch there, sorry I'm not expert with test-control module. About non-auto generated keys, you should not have problem, really was a isolate bug. On Fri, Jul 10, 2015 at 3:57 PM, akm wrote: > I had another question > Since this was due to the non portability of

Re: Cascade persist and merge with Repository.

2015-07-10 Thread akm
I had another question Since this was due to the non portability of non-auto generated keys, is there any other impact of using non-auto generated keys? We use uuids and was just wondering if you have any recommendations on the usage of generated sakeys versus uuids for primary key. Thanks -- Vi

Re: Cascade persist and merge with Repository.

2015-07-10 Thread akm
*The unit test console log just displays -* Jul 10, 2015 3:14:46 PM org.apache.deltaspike.testcontrol.api.junit.CdiTestSuiteRunner$LogRunListener testFailure INFO: [failed] test.com.myApp.it.test.CascadeTestWithRepository#createBookingWithRepository message: Failed calling Repository: [Repository=c

Re: Cascade persist and merge with Repository.

2015-07-10 Thread Daniel Cunha
Akm, weird, here deltaspike return this: Failed calling Repository: [Repository=com.myApp.entities.BookingRepository,entity=com.myApp.entities.Booking,method=save,exception=class java.lang.IllegalStateException,message=During synchronization a new object was found through a relationship that was

Re: Cascade persist and merge with Repository.

2015-07-10 Thread Daniel Cunha
Akm, looking for it. On Fri, Jul 10, 2015 at 11:40 AM, akm wrote: > Thanks. This works now. > > The exception that I get has a null message. Is this intentional or should > it have the EclipseLink error message? > *The EclipseLink error is -* > Caused by: java.lang.IllegalStateException: During

Re: Cascade persist and merge with Repository.

2015-07-10 Thread akm
Thanks. This works now. The exception that I get has a null message. Is this intentional or should it have the EclipseLink error message? *The EclipseLink error is -* Caused by: java.lang.IllegalStateException: During synchronization a new object was found through a relationship that was not marke

Re: Cascade persist and merge with Repository.

2015-07-10 Thread Daniel Cunha
+1 On Fri, Jul 10, 2015 at 5:24 AM, Gerhard Petracek wrote: > fyi: > the snapshot-deployment via ci-job is active again. > > regards, > gerhard > > > > 2015-07-09 19:18 GMT+02:00 Gerhard Petracek : > > > i just deployed a new snapshot manually. > > > > regards, > > gerhard > > > > > > > > 2015-0

Re: Cascade persist and merge with Repository.

2015-07-10 Thread Gerhard Petracek
fyi: the snapshot-deployment via ci-job is active again. regards, gerhard 2015-07-09 19:18 GMT+02:00 Gerhard Petracek : > i just deployed a new snapshot manually. > > regards, > gerhard > > > > 2015-07-09 17:03 GMT+02:00 akm : > >> Do you have any estimate on when the snapshot will be ready? >

Re: Cascade persist and merge with Repository.

2015-07-09 Thread Gerhard Petracek
i just deployed a new snapshot manually. regards, gerhard 2015-07-09 17:03 GMT+02:00 akm : > Do you have any estimate on when the snapshot will be ready? > > > > -- > View this message in context: > http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-

Re: Cascade persist and merge with Repository.

2015-07-09 Thread akm
Do you have any estimate on when the snapshot will be ready? -- View this message in context: http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository-tp4661002p4661025.html Sent from the Apache DeltaSpike Incubator Discussions mailing list

Re: Cascade persist and merge with Repository.

2015-07-09 Thread Daniel Cunha
Ah.. thanks Gerhard. :) On Thu, Jul 9, 2015 at 10:54 AM, Daniel Cunha wrote: > Hmm, > > not deployed to nexus yet. (I don't have acknowledgment about this process > [snapshot nexus deploy]) > You can build the source as well. > > > On Thu, Jul 9, 2015 at 10:24 AM, akm wrote: > >> I just got th

Re: Cascade persist and merge with Repository.

2015-07-09 Thread Daniel Cunha
Hmm, not deployed to nexus yet. (I don't have acknowledgment about this process [snapshot nexus deploy]) You can build the source as well. On Thu, Jul 9, 2015 at 10:24 AM, akm wrote: > I just got the 1.4.2-SNAPSHOT from the > http://repository.apache.org/snapshots > repository, but it still be

Re: Cascade persist and merge with Repository.

2015-07-09 Thread Gerhard Petracek
hi, currently you have to build the snapshot manually, because there is an infra-issue. regards, gerhard 2015-07-09 15:24 GMT+02:00 akm : > I just got the 1.4.2-SNAPSHOT from the > http://repository.apache.org/snapshots > repository, but it still behavahes the same way. > > I do not see any c

Re: Cascade persist and merge with Repository.

2015-07-09 Thread akm
I just got the 1.4.2-SNAPSHOT from the http://repository.apache.org/snapshots repository, but it still behavahes the same way. I do not see any change in the isNew method code. public boolean isNew(Object entity) { try { return entityManager.getEntityManagerFacto

Re: Cascade persist and merge with Repository.

2015-07-08 Thread Daniel Cunha
Hi Akm, Fixed in SNAPSHOT. you can test with it (1.4.2-SNAPSHOT). Thank you for reporting. On Wed, Jul 8, 2015 at 5:21 PM, akm wrote: > I will try to override the isNew method. > > We have non auto generated keys for what we consider "Lookup" type of > Entities. example country, city, state. >

Re: Cascade persist and merge with Repository.

2015-07-08 Thread akm
I will try to override the isNew method. We have non auto generated keys for what we consider "Lookup" type of Entities. example country, city, state. -- View this message in context: http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Cascade-persist-and-merge-with-Repository

Re: Cascade persist and merge with Repository.

2015-07-08 Thread Daniel Cunha
Hi akm, you have 2 entity where ID isn't auto generated the problem is: he set ID of the parent and ID of the children. you call the save of the entityRepository entityRepository.save call merge, because for it, it isn't a new Entity. We use PersistenceUnitUtil for check it, but see the javadoc f

Re: Cascade persist and merge with Repository.

2015-07-08 Thread Daniel Cunha
Akm, I'm looking for it. Thank you. :) On Wed, Jul 8, 2015 at 12:59 PM, akm wrote: > I have attached a simple gradle CascadeRefreshGradleTestProject.zip > < > http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/file/n4661005/CascadeRefreshGradleTestProject.zip > > > project

Re: Cascade persist and merge with Repository.

2015-07-08 Thread akm
I have attached a simple gradle CascadeRefreshGradleTestProject.zip project with unit tests. -- View this message in context: http://apache-deltaspike-incubator-discussio

Re: Cascade persist and merge with Repository.

2015-07-07 Thread Daniel Cunha
On Tue, Jul 7, 2015 at 6:17 AM, Gerhard Petracek wrote: > hi, > > please provide a simple demo-application (including the test) which > illustrates the issue. > +1 > i tested it locally and everything looks fine (here the test fails as > expected). > Me too. Work fine here. :) > > regards, >

Re: Cascade persist and merge with Repository.

2015-07-07 Thread Gerhard Petracek
hi, please provide a simple demo-application (including the test) which illustrates the issue. i tested it locally and everything looks fine (here the test fails as expected). regards, gerhard http://www.irian.at Your JavaEE powerhouse - JavaEE Consulting, Development and Courses in English and