• 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
  • Rob Spoor
  • Tim Cooke
  • Junilu Lacar
  • Henry Wong
  • Liutauras Vilda
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Tim Holloway
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • Al Hobbs
  • Mikalai Zaikin
  • Piet Souris

EJB 2 : Query in understanding Transaction Attribute NotSupported

Ranch Hand
Posts: 2234
Eclipse IDE Firefox Browser Redhat
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

The Container invokes an enterprise Bean method whose transaction attribute is set to NotSupported with an unspecified transaction context.

I am having a query in understanding the above thing .Please let me know what does above mean and also what transaction context mean in the below :

If a client calls with a transaction context, the container SUSPENDS the association of the transaction context with the current thread before invoking the enterprise bean's business method.

Thanks in advance .

Ranch Hand
Posts: 247
Eclipse IDE Chrome Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Transaction context is nothing but the meaningful transaction... A group of methods can be executed in one transaction... If any method fails, the whole transaction can be rolled back i.e., undo the activities done by previous methods...

For e.g.,

M1 M2 M3 ... There are three methods...

Suppose M1 and M2 method execution is successful and M3 method call comes under the same transaction chain... If M3 fails, the activities done by M1 and M2 can be rolled back since these three method issue-less execution is considered as successful...

If it was called under no transaction context, previous methods action cannot be undone...

Thats the great advantage of transaction context...

And NotSupported attribute refuses to run under transaction context... that is,

M1 is called under "Transaction Context" and M2 is marked as "NotSupported"... At that time, same transaction context is not carried over to M2 and M2 run under no transaction context... Actions performed by M2 cannot be undone.. Since its out of transaction context
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    Bookmark Topic Watch Topic
  • New Topic