Bug 36689 - TxXMLFileDescriptorStore vs. AbstractTxFileStore - threadlocal collission?
Summary: TxXMLFileDescriptorStore vs. AbstractTxFileStore - threadlocal collission?
Status: RESOLVED INVALID
Alias: None
Product: Slide
Classification: Unclassified
Component: Stores (show other bugs)
Version: Nightly
Hardware: Other other
: P2 major (vote)
Target Milestone: ---
Assignee: Slide Developer List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-09-16 18:17 UTC by Gregory Block
Modified: 2006-07-20 09:44 UTC (History)
0 users


Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gregory Block 2005-09-16 18:17:46 UTC 
In TxXMLFileDescriptorStore, various parts do things like:
activeTransactionBranch.set(txContext);

but in the AbstractTXFileStore service, you get requests like...
activeTransactionBranch.set(txId);

- With completely different types.

So, here's the question:  Was it *intended* that TxXMLFileDescriptorStore would be overwriting the 
contents of activeTransactionBranch's thread local data with an object of a different type?
Comment 1 Oliver Zeigermann 2006-07-20 16:44:30 UTC 
This is intended. Have a look at the different implementations of
getActiveTxId() in both classes for an explanation.