○ 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
might be
more useful... although having a hard time understanding if this matters in
the context of the DeltaSpike JPA abstraction?]
Any guidance? Or more specifically, have you been doing any work/testing
with queries and multicore processing?
_Marvin
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 what is better
for you.
On Fri, Jul 10, 2015 at 4:15 PM, akm <amehta5@> wrote:
> 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-deltaspike-incubator-discussions.2316169.n4.nabble.com/Scope-of-Entity-Manager-tp4661043p4661048.html
Sent from the Apache DeltaSpike Incubator Discussions mailing list archive at
Nabble.com.
