How to implement own TransactionManagment

[walter wang]

I had a java application ( desktop application, standalone program)

How could I implement my own TransactionManagment for it?
my application doesnot do anything with Database.


Could anyone give some hints?

[Jeff Storey]

Hi Walter,

You should look into using synchronization or locks. They allow you to "protect" code so only one thread can enter it at a time. Consider this:

public class MyClass {
   public synchronized void methodA() {
       for ( int i = 0; i < 1000; i++ ) {
           System.out.println("in method A " + i);
       }
    }
   public synchronized methodB() {
       for ( int i = 0; i < 1000; i++ ) {
           System.out.println("in method B " + i);
       }
    }
 
    Thread a = new Thread() {
        public void run() {
            methodA();
         }
    };
 
    Thread b = new Thread() {
        public void run() {
            methodB();
         }
    };
    a.start();
    b.start();
}
 

In this case, either all of method A will run before method B or the other way around (depending on which thread actually starts first, a or b). Since both methods are synchronized, only one thread can hold the lock at any given time. Check out this example. http://www.d.umn.edu/~gshute/java/synchronization.html.

Hope this helps.

Jeff

[Nitesh Kant]

walter:
How could I implement my own TransactionManagment for it?

Well Transaction management is a big big monster. No one can explain it to you in a single post.
If you want to write your own Transaction Management then it is better to follow JTA and JTS.

walter:my application doesnot do anything with Database.

Well transaction management does not always deal with database handling. Transactions is a way to guarantee ACID(Atomicity, Consistency, Isolation and durability) properties. It can be applied to any system and any process.

For example in my POJO I can call two methods, such that, the second method is called only if the first succeed and if the second fails the result of the first operation must be reverted.
Even if the above methods do not make any database calls or any other data persistance calls, it still can be addressed by Transaction Management.

[walter wang]

Originally posted by Jeff Storey:
Hi Walter,

You should look into using synchronization or locks. They allow you to "protect" code so only one thread can enter it at a time. Consider this:

public class MyClass {
   public synchronized void methodA() {
       for ( int i = 0; i < 1000; i++ ) {
           System.out.println("in method A " + i);
       }
    }
   public synchronized methodB() {
       for ( int i = 0; i < 1000; i++ ) {
           System.out.println("in method B " + i);
       }
    }
 
    Thread a = new Thread() {
        public void run() {
            methodA();
         }
    };
 
    Thread b = new Thread() {
        public void run() {
            methodB();
         }
    };
    a.start();
    b.start();
}
 

In this case, either all of method A will run before method B or the other way around (depending on which thread actually starts first, a or b). Since both methods are synchronized, only one thread can hold the lock at any given time. Check out this example. http://www.d.umn.edu/~gshute/java/synchronization.html.

Hope this helps.

Jeff

Thanks for your suggestion. yeah. it solves the synchronization problem,but how it handle rollback when excpetion happens?...
example rollback deleted files..or...

[walter wang]

Originally posted by Nitesh Kant:


Well transaction management does not always deal with database handling. Transactions is a way to guarantee ACID(Atomicity, Consistency, Isolation and durability) properties. It can be applied to any system and any process.

For example in my POJO I can call two methods, such that, the second method is called only if the first succeed and if the second fails the result of the first operation must be reverted.
Even if the above methods do not make any database calls or any other data persistance calls, it still can be addressed by Transaction Management.

>>>> could you please give me some hints (sample code) for your mentioned roll back feature? it is just what I am looking for....