[Bug 267] New: Generic identification of context

[bugzilla-daemon@arjuna.com]

http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=267

           Summary: Generic identification of context
           Product: WS-Context
           Version: 1.0
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Model
        AssignedTo: ws-caf@lists.oasis-open.org
        ReportedBy: kevin.conner@arjuna.com
         QAContact: mark.little@arjuna.com


A recent change has altered the mechanism for transporting contexts.

The previous mechanism wrapped all contexts, derived or otherwise, within a
header element of QName wsctx:context.  As all context headers shared the same
element QName, it was possible to identify the context headers without knowledge
of the specific context(s) being transported.

The current model forces referencing specifications to identify their context
using a unique header element QName.  The consequence of this decision is that
it is no longer possible to identify which headers contain a context without, at
the very least, having knowledge of each context element QName.

I believe there is a case for allowing the identification of header context
elements without requiring predetermined knowledge of their QNames and that, in
the current model, we are being too restrictive.

The emails referenced below detail one specific use case, I'm sure others can
come up with more.

http://www.oasis-open.org/apps/org/workgroup/ws-caf/email/archives/200506/msg00026.html
http://www.oasis-open.org/apps/org/workgroup/ws-caf/email/archives/200506/msg00029.html



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.