I have a situation where I want to use a transaction to keep track of a particular message process in order to roll back various parts if there is a failure. The service operation is listening on a queue using the NetMSMQBinding and the operation is marked with the transaction properties of the OperationBehavior like so: <OperationBehavior(Trans... Public Sub SendHello( ... Using the above attribute enables the operation for transaction...

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/VrG

Disclaimer: This post speaks from an outsiders perspective. My interactions with this initiative have been from a regional implementers standpoint and I am not privy to any of the decisions that led to the OneDOJ initiative. This perspective comes from actual project work and reviewing open source information regarding the broader initiative. One of my first web service projects involved implementing a service from a WSDL provided to us by the federal partner in charge of a regional data sharing...

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/VoI

One of the goals of a large state-wide multi-agency data sharing project my organization is participating in was to start with a partner designed WSDL and then implement it in the underlying technology of the partner's choice. For my organization this technology is Windows Communication Foundation. From it's inception the WSDL had to be simple and interoperable. This is the second time I had started with a WSDL and then created a conformant service. My organization was one of the few that actually...

• Share This Post:
• 
• 
• 
•   Short Url: http://wblo.gs/VoG