Re: Scope of Entity Manager

hi marvin, when it comes to concurrency both are similar. the request- as well as the transaction-context store instances in a ThreadLocal variable/storage. regards, gerhard 2015-07-10 21:53 GMT+02:00 MarvinToll : > ○ A couple of factors that we have been considering in making the decision >

Re: Scope of Entity Manager

○ A couple of factors that we have been considering in making the decision include: 1. Small data vs. large data [presumption that big data may benefit from early de-referencing of the EntityManager L1 cache [UOW] ) 2. Provisioning for multicore [presumption that @TransactionScoped

Re: Cascade persist and merge with Repository.

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: Scope of Entity Manager

Akm, @RequestScoped: EntityManager is producing it as request scoped bean means that the disposer method will be called on finishing the request. @TransactionScoped: Will be closed after leaving the method annotated with @Transactional. That will depend on the your architecture, you can select w

Re: Cascade persist and merge with Repository.

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

Scope of Entity Manager

Does DeltaSpike have any recommendation on the the scope of the Entity Manager that will be used by the Repository? I have tried both the @RequestScoped and the @TransactionScoped and would like to know which DeltaSpike recommends and why. Thanks -- View this message in context: http://apache-d

Re: Cascade persist and merge with Repository.

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.

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.

*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.

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.

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: Start Request scope manually fro a worker thread(asynchronous thread) in WAS8

Thank you Mark... That did work.. Now RequestScope is available for the Batch(Async) Jobs. -- View this message in context: http://apache-deltaspike-incubator-discussions.2316169.n4.nabble.com/Start-Request-scope-manually-fro-a-worker-thread-asynchronous-thread-in-WAS8-tp4661026p4661038.html Se

Re: Cascade persist and merge with Repository.

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: Start Request scope manually fro a worker thread(asynchronous thread) in WAS8

Think you even need to taken an older version https://svn.apache.org/repos/asf/openwebbeans/tags/openwebbeans-1.0.0/webbeans-test/cditest-owb/src/main/java/org/apache/webbeans/cditest/owb/ > Am 10.07.2015 um 14:33 schrieb Mark Struberg : > > The problem I got when I tried this was that the CDI p

Re: Start Request scope manually fro a worker thread(asynchronous thread) in WAS8

The problem I got when I tried this was that the CDI part was perfectly working. But all the com.ibm.ws.* EJB interceptors you get did blow up because those parts were not set up. Sadly this hits you on more CDI beans than you expect :( As DeltaSpike CdiCtrl was originally the openwebbeans test

Re: Cascade persist and merge with Repository.

+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

first steps for the next release

hi @ all, if there are no objections, i will start with the first steps for the next release (v1.4.2) by the end of next week. regards, gerhard

Re: Cascade persist and merge with Repository.

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? >