I have to keep up with the transaction by hand in an approach to a category that was marked as @Transactional. Basically try to get this done now, the best has been tossed (most most likely since the transaction has been committed two times, once by me, and two times through the wrapper proxy). What should i do.

If this isn't possible, then it is possible to method of getting informed whenever a transaction was effectively committed (data within the DB and everything), to ensure that I call another applciation, which relies on a single DB?

I think you'll are utilizing spring. If so, you'll be able to.

Look at this block of code in the API here. at section 10.5.6 Using @Transactional

@Transactional(readOnly = true)
public class DefaultFooService implements FooService {

 public Foo getFoo(String fooName) {
// do something
}

// these settings have precedence for this method
@Transactional(readOnly = false, propagation = Propagation.REQUIRES_NEW)
public void updateFoo(Foo foo) {
 // do something
}
}

No, I do not believe you could do. In my opinion should you create another thread and execute the code, it will likely be outdoors from the transaction though. Be cautious with this, since it could possibly get dicey when you're creating additional threads and controlling that yourself.