• Post Reply Bookmark Topic Watch Topic
  • New Topic

Design Decision - Transactions  RSS feed

 
AJ Phruksukarn
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,

I'm currently designing a system that must perform atomic transactions across multiple databases and file-systems. I was wondering if anyone had any advice as to which approach/technology to use. I know EJB's can handle database transactions, but can they incorporate data and file transfers all into one transaction, or do I need to look elsewhere? Also, if my sysadmin will not allow the deployment of an application server are there any other options I can look at?

Thanks in advance for any wisdom the community can share.

AJ
 
Balaji Akella
Ranch Hand
Posts: 35
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
JTA is the API, which would allow you to implement distributed transactions spanning accross multiple databases. I am not sure about, having a file system updates, within the same transaction.

If your application cannot be deployed on an, J2EE app server, you can consider utilizing the JTA API directly.

Swamy
 
It is sorta covered in the JavaRanch Style Guide.
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!