• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Jeanne Boyarsky
  • Bear Bibeault
  • Rob Spoor
  • Henry Wong
  • Liutauras Vilda
Saloon Keepers:
  • Tim Moores
  • Carey Brown
  • Stephan van Hulst
  • Tim Holloway
  • Piet Souris
  • Frits Walraven
  • Himai Minh
  • Jj Roberts

CMT NOT_SUPPORTED and REQUIRED transactional behavior

Posts: 9
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi all

I have this scenario:

EJB1 have a method handler(List<UserDTO> users) annotated with : @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED). In this method I call other EJB2 method annoted with @TransactionAttribute(TransactionAttributeType.REQUIRED).

The goal is to have transaction only on single saveUser operation and not on complete users list.
If I have understod cmt transacation behavior the NOT SUPPORTED doesn't start a new transaction on handler() method,but create one when saveUser is called. is this right?

Thank you for suggests!
Once upon a time there were three bears. And they were visted by a golden haired tiny ad:
SKIP - a book about connecting industrious people with elderly land owners
    Bookmark Topic Watch Topic
  • New Topic