|
| Does anyone has an idea how to implement the following:
Situation:
1.We send out our request and wait for a response. We don't wait forever, if
the other side does not reply within a given timeout, we compose a timeout
message in our orchestration and send it to our application. By sending this
timeout message the orchestration is completed. If we then receive the reply
from the other side, the correlation is gone! Resulting in an error message
(our server sends them an 'internal server error')
2. The 'other side' sometimes sends a type of message for which we don't
have an orchestration to handle.
What I need to do now is implement error handling for these two scenarios:
If the correlation is gone or we receive a message that does not match any
orchestration (or bad XML) we need to send an XML file to 'the other side'
telling them that their XML is bad. (not sending the internal server error)
Who knows how to do this?
Thanks,
Peter
|
|