[wildfly-dev] discussion about JSR352 Batch and JPA

[Cheng Fang]

If the ItemReader, ItemWriter in the batch application reads from, or 
writes to jms destinations, these operations are also transactional.  
The batch container will manage the transaction the same way as with 
database access.

Cheng

On 9/18/13 2:24 PM, Clebert Suconic wrote:
> Maybe I'm getting late on the conversation.. wouldn't JMS also apply into Transactional batching?
>
>
> On Sep 18, 2013, at 1:43 PM, Jason Greene <jason.greene at redhat.com> wrote:
>
>> On Sep 18, 2013, at 7:54 AM, Scott Marlow <smarlow at redhat.com> wrote:
>>
>>> What are the requirements for supporting Batch section 11.6 [1]?  From
>>> looking at JSR352, I get that each "chunk" has its own JTA transaction.
>>> I previously had heard that we only supported starting the transaction
>>> from the application processing code (via UserTransaction) but I think
>>> the Batch container/runtime should start a JTA transaction for each
>>> "chunk" that is processed.  What are we really doing for managing the
>>> JTA transactions for batch?
>>>
>>>
>>> REGULAR CHUNK PROCESSING & JPA
>>>
>>>
>>> For the JPA support for regular chunk processing [1], the following will
>>> give a new underlying persistence context per chunk (jta tx):
>>>
>>> @PersistenceContext(unitName = "chunkNonpartitionedAZTT4443334")
>>> EntityManager em;
>>>
>> That won't work because the same block of code is executed in parallel from 2 different threads. Each chunk needs a clean entity manager.
>>
>>
>> --
>> Jason T. Greene
>> WildFly Lead / JBoss EAP Platform Architect
>> JBoss, a division of Red Hat
>>
>>
>> _______________________________________________
>> wildfly-dev mailing list
>> wildfly-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev