+972 52-548-6969
Funny comments
time to read 2 min | 207 words
I don’t know what the story behind this is, but I really want to:
/** * Determine an identifier for the given transaction appropriate for use in caching/lookup usages. * <p/> * Generally speaking the transaction itself will be returned here. This method was added specifically * for use in WebSphere and other unfriendly JEE containers (although WebSphere is still the only known * such brain-dead, sales-driven impl). * * @param transaction The transaction to be identified. * @return An appropropriate identifier */ public Object getTransactionIdentifier(Transaction transaction);
This is part of the Hibernate source code.
Comments
The story is that IBM hasn't published any documentation how to integrate your persistence management layer with Websphere transaction manager.
For simplest scenarios you will be fine with default simulated transactions. But if you're using multiple transactional resources then WebSphere's transaction manager is the way. Hibernate's approach (which is correct) is trying to utilize Websphere transaction manager - since there is no documentation on that, it is understandable developer frustration. :) Most of that feature was developed using trial/error approach :)
Comment preview