[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: Error to use when P-Mode not found
1. Yes – already encountered situations this where PModes are varied – no way for Client to discover them; they need to be assigned on basis of inbound unique property. Any HTTP side element (URL; IP address etc) can be mangled by routers etc and lost. We are using the ebMS Form field to index agreed PModes and load these at runtime; but there are cases where these are not known ahead of time and I think it better to return as specific a message as possible.
2. Can we add a new Error to specifically cover this situation? Ie PModes Unknown – ie not set up in advance. Not actually an error - normally applies to a new or not configured connector attempts.
Not sure what the specific process is – ie mod to update Spec – how easy or hard is this?
Oban Pty Ltd | Ground Floor 19-23 Prospect St | Box Hill 3128 | Australia
ABN 18 163 365 080
T: +61 3 9044 1702 | M: 0408 017 962 | F: +61 3 9044 1799
The recipient of this e-mail is solely responsible for conducting such tests and virus scanning as may be necessary, before using any attachment, to ensure that the attachment does not contain any virus and that use of the attached materials will in no way corrupt the recipient's data or systems or those of any other person.
I have some questions I would like to discuss with you about the Error that should be returned if an MSH can not determine which P-Mode should handle a received message.