Scott,

I read Chapter 8 fully and I understand what is written as far as transactions are concerned. What I am confused about is how a rollback is called. Also, what code needs to be written to get acknowledgement of the rollback so the rollback can occur.

In addition, how do you "bundle" multiple client calls into a transaction or are transactions only within a specific Operation on the server side?

Thanks

Hi jamocle,

I am finishing up the Message contract example in chapter 6 currently and will answer this by the end of the week.

Thanks...

Scott

========================
Scott Klein
Author of:
Professional SQL Server 2005 XML
Professional WCF Programming: .NET Development with the Windows Communication Foundation
Professional LINQ
========================

Scott,

Any information on this one yet?

Scott,
Any information on this yet?

Thanks

James

Oops! I completely forgot about this! I will look at this right now and get back to you.

========================
Scott Klein
Author of:
Professional SQL Server 2005 XML
Professional WCF Programming: .NET Development with the Windows Communication Foundation
Professional LINQ
========================

OK, here is what I found. Just for clarification I spoke with WCF transaction person, and got the following feedback:

If the transaction is not complete (you have some methods with TransactionAutoComplete=false which is not the default) AND you terminate the session by calling an IsTerminating method, the transaction will Commit. Rollback will typically occur when exceptions happen (user or system).


To receive transaction notifications, take a look at the IEnlistmentNotification interface (http://msdn2.microsoft.com/en-us/lib...ification.aspx).

Then at EnlistVolatile (http://msdn2.microsoft.com/en-us/lib...tvolatile.aspx) for examples of how to do this.

Basically what will happen is you’ll register a class which will receive various transaction messages (prepare, commit, rollback) and you’ll be expected to handle those notifications correctly. (Transaction.Current.EnlistVolatile(new MyNotificationClass(), EnlistmentOptions.None))



========================
Scott Klein
Author of:
Professional SQL Server 2005 XML
Professional WCF Programming: .NET Development with the Windows Communication Foundation
Professional LINQ
========================

Scott,

I performed the EnlistVolatile along with the IEnlistmentNotification interface. When I turn off Transactions in WCF I get the prepare, commit, rollback, etc, but I, of course do not get information flowed back to the client.

When I turn on Transaction flowing all I get is the rollback, no commit or prepare. It looks like WCF enlists prior to me being able to prepare which is killing my ability to write server side transactions.

Help please!!!

Jamocle

Hi Jamocle,

Sorry for the late reply. I will look into this today and get back with you (I am not in the office right now) but I will reply within the next 24 hours.

========================
Scott Klein
Author of:
Professional SQL Server 2005 XML
Professional WCF Programming: .NET Development with the Windows Communication Foundation
Professional LINQ
========================

Scott,

Any news yet? I am anxiously awaiting.

The EnlistVolatile has two overloads, one which supports a two phase commit and another which supports a single phase commit. The IEnlistmenetNotification enlists a volatile resource that supports a two phase commit transaction. You should be able to do something like:

using (TransactionScope scope = new TransactionScope())
{

  //Create an enlistment object
  myEnlistmentClass myElistment = new myEnlistmentClass();

  //Enlist on the current transaction with the enlistment object
  Transaction.Current.EnlistVolatile(myElistment, EnlistmentOptions.None);

  //Perform transactional work here.

  //Call complete on the TransactionScope based on console input
  ConsoleKeyInfo c;
  while(true)
  {
    Console.Write("Complete the transaction scope? [Y|N] ");
    c = Console.ReadKey();
    Console.WriteLine();
    if ((c.KeyChar == 'Y') || (c.KeyChar == 'y'))
    {
      scope.Complete();
      break;
    }
    else if ((c.KeyChar == 'N') || (c.KeyChar == 'n'))
    {
      break;
    }
  }
}

It also depends on now you implement transactions, meaning, in some cases you need to commit/rollback manually. I need to go look, but I think this chapter covers that...i'll grab a copy of my book and look.

Also, you may need to look at the EnlistDurable method, which let's you get a durable enlistment in a transaction.

I'll repost shortly after I verify a few things...


========================
Scott Klein
Author of:
Professional SQL Server 2005 XML
Professional WCF Programming: .NET Development with the Windows Communication Foundation
Professional LINQ
========================