[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: ebXML Headers Doc for Tokyo
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. "Patil, Sanjay" wrote: <snip> > 5> Can we have a single rule for relation betwen DocumentLabel > and Action values ex. > Action = DocumentLabel + "Action" > Use of "create" and "receive" delve into the semantics of > the business process and does not necessarily cover all > possibilities ex. "change" for changing an existing Purchase Order > <snip> -- Regards, Farrukh
begin:vcard n:Najmi;Farrukh tel;fax:781-442-1610 tel;work:781-442-0703 x-mozilla-html:TRUE url:www.sun.com org:Sun Microsystems;Java Software adr:;;1 Network Drive, MS BUR02-302;Burlington;MA;01803-0902;USA version:2.1 email;internet:najmi@east.sun.com fn:Farrukh S. Najmi end:vcard
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC