Win a copy of Learning OpenStack Networking: Build a solid foundation in virtual networking technologies for OpenStack-based clouds this week in the Cloud/Virtualization forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Knute Snortum
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Ganesh Patekar
  • Stephan van Hulst
  • Pete Letkeman
  • Carey Brown
Bartenders:
  • Tim Holloway
  • Ron McLeod
  • Vijitha Kumara

HFEJB Question  RSS feed

 
Ranch Hand
Posts: 643
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
HFEJB Pno-556
I am not able to solve below given points-:

A bean realizes it cannot commit a transaction,but it does not want the client to get an exception.what can the bean do?

A bean wants the client to get an application exception but the bean still wants the transaction to commit.what should bean do?

Please Help
Thanks
 
Ranch Hand
Posts: 218
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

A bean realizes it cannot commit a transaction,but it does not want the client to get an exception.what can the bean do?

A bean wants the client to get an application exception but the bean still wants the transaction to commit.what should bean do?



I can think of this,

If the bean throws system exception, transaction will rollback and an exception will be thrown to client. We dont want this.

The only way is to call setRollbackOnly() and mark the transaction to rollback.


Regarding the second one,
If our method has declared the application exception in the signature
and throws it, the container will not rollback the transaction and
throw the exception to client.

What do you think? Is it right?
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!