[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: ebXML Headers Doc for Tokyo
Message text written by Farrukh Najmi > Sanjay, I have a problem with #5. Why does the Action have to have DocumentLabel with the suffix "Action" ? Why should the DocumentLabel alone not be sufficient? It is unique within the ServiceInterface. I use the action in my RR impl to map to a method call within the interface directly. Your suggestion would require me to parse the "Action" suffix out. Can we just stick with: Action = DocumentLabel BTW, If you have some cycles please look over the RR TRP messages I sent as a sanity check. Thanks for your help and support. <<<<<<<<<<<<<<<<<<<<< Farrukh. This seems unreliable. I'm using the combination of the header and the payload, since the RR payload explicitly names the action required; that should take prescedence over the header in anycase. The header may just have generic information - depending on the diligence of the sender. DW.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC