[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [Bug 133] New: context by value and context by reference should be different types
http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=133 Summary: context by value and context by reference should be different types Product: WS-Context Version: 1.0 Platform: PC OS/Version: Windows 2000 Status: NEW Severity: normal Priority: P2 Component: Schema AssignedTo: ws-caf@lists.oasis-open.org ReportedBy: peter.furniss@choreology.com QAContact: mark.little@arjuna.com a context-by-value - whether passed as a header, or as returned by dereferencing a context-by-reference - contains elements concerned with whatever it is being used for - some of these are defined in ws-context, some will be defined in referencing specifications. a context-by-reference, on the other hand, does not contain these elements, but does need to contain some others - in particular the information needed for the dereference. It would seem unlikely that a referencing specification would add elements to the reference form (possibly it should be explicitly prohibited, as it would complicate the implementation of the dereferencing capability) It is confusing to represent these two different constructs as the same xml type with optional fields. They should be separate types, with mandatory fields where the required mechanisms would not work interoperably if the field were absent. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]