[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Requirement to have first all CanSend elements, followed by allCanReceive elements. Changing Schema so that the order does not play a role?
Hi team Today I had to write up a CPA. There was one CollaborationRole element. Within the ServiceBinding of that CollaborationRole were many CanSend and CanReceive elements. I was adding buisness signals (ReceiptAcceptance and ReceiptException) as CanSend, CanReceive elements within the ServiceBinding. So the inteded grouping was: one business transaction activity by one within a business transaction activity first business messages, followed by the busines signals. Then I was surprised that my CPA did not validate against the schema. To satisfy the schema I had to regroup by: first all CanSend elements followed by all CanReceive elements. I think it does not make sense to require to list first all CanSend followed by all CanReceive. It would be easier to let end users mix CanSend and CanReceive elements. Dale, I think this is would be a small CPPA Schema change and still be backwards compatible. What do you think? Sacha
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]