[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: Party XML Schema Defintions
Message text written by Martin Bryan >> > This would also depracate the need for the <communicationPoint> > element. The CPP would be grabbed from a Registry using the default > static Registry CPA (RIM??). No, No, No. You should not need to refer to the registry from every message. Message types are linked to the registry, not message instances. Information that is instance specific should remain a part of the message. If as a part of message validation you want to check that the message contents match the CPP contents then you do a match, using XSLT, between the contents of one element in the instance with the contents of the referenced CPP document. You do not expect the data required by the user to be taken from the registry because you cannot guarantee access to it will not be denied at a critical time. Martin< >>>>>>>>>>>>>>>> Martin, I think you extrapolated this - you would only need to do this on the first occurence of a new CPP - or a change of CPP version (same thing). Thereafter you would have it cached locally. DW.
Powered by eList eXpress LLC