| Chris C. 2006-02-20, 5:52 pm |
| I have to modify an orchestration that is currently an atomic transaction.
When BizTalk exceptions occur, the orchestration is terminated and the XML
message is not recoverable. I need to update the orchestration so I can
catch BizTalk generated exceptions and allow for the XML message to be
recoverable.
I would like to access the XML message and the associated error information
during the time of the BizTalk exception. I would like to write the error
information to the event log and capture the XML message at the time of the
exception and also put it to the error log if possible. Also, if possible, I
would like to suspend the orchestration so the XML message can be
recoverable. There are variables and message variables that are global to
the atomic orchestration. I would like to access these global orchestration
variables within the exception error handling routine. If I can access the
message variable and the other global variables within the exception error
handling routine, it would possibly simplify my error handling routine.
What would be the best solution for all of this? I need to keep the
orchestration atomic somehow because of non-serialized variables - event log
variable (that comes from System.Diagnostics.EventLog) and XMLnode variable
(that comes from System.Xml.XmlNode).
Chris C.
|