you know what a scope of a variable mean,i mean the scope in which the variable is valid...that way transaction scoping means the extent of the transaction....here in the option B it says MDB's need not be in a transaction...which is false ...since MDB's are a part of the transactions hope this helps tx Pradeep
The question asks about what is true about container support of MDB's and "B" says the container is NOT required to support scoping (and the answer is not checked, therefore the question suggests that the container IS required to support scoping). After looking through the spec, I still don't REALLY know what they mean by "transaction scoping". My first thought was that since, in the case of MDB's, there is no related previous transaction, and there is no related follow-on transaction, the container's job is easier (it doesn't have to suspend, or require new or any of that). But apparently that is NOT transaction scoping. Would it be true to say that "transaction scoping" includes the tasks that the container performs to support a transaction? In that case, the container would always be required to support transaction scoping. That's a better question: "is there ever a case where the container is NOT required to support transaction scoping"? If there is no such case, then this is much ado about nothing. --Dale-- [ April 22, 2004: Message edited by: Dale Seng ]
Post by:autobot
Farmers know to never drive a tractor near a honey locust tree. But a tiny ad is okay:
a bit of art, as a gift, that will fit in a stocking