SOAP-JMS Binding Working Group
Issue Tracking
Summary
Issues:
Raised
Open
Closed
All
Create
Actions:
Open
Overdue
Closed
Pending Review
Raise
Users
My
Tracker
Products
Agenda planning
Recent activity
Open Actions
Apply the following changes to selected action items:
Mark as
No status change
Open
Pending review
Closed
Update due date to:
Associate to issue:
No change
ISSUE-1: Assert Protocol-2013 is spurious
ISSUE-2: Protocol-2020 is spurious
ISSUE-3: Protocol-2023 is spurious
ISSUE-4: Protocol-2024 needs restructuring
ISSUE-5: Protocol-2035 is redundant
ISSUE-6: Protocol 2039 redundant
ISSUE-7: Protocol-2041 is spurious
ISSUE-8: Incorrect example, section C2
ISSUE-9
ISSUE-10: redundant assertions 2016 and 2017
ISSUE-11: requestURI in response message?
ISSUE-12: Bad MIME terminating boundary
ISSUE-13: Extra space in Schema
ISSUE-14: WSDL conformance statements missing
ISSUE-15: Incorrect use of RFC keywords
ISSUE-16: non-existent "soap" prefix
ISSUE-17: References to RFC 3987
ISSUE-18: consistency of references, acronyms
ISSUE-19: 3001, 3002, 3003 overlap
ISSUE-20: Statement 3004 lacks context, RFC 2119 keywords
ISSUE-21
ISSUE-22: mphillip
ISSUE-23: mphillip
ISSUE-24: mphillip
ISSUE-25: mphillip
ISSUE-26: mphillip
ISSUE-27: mphillip
ISSUE-28
ISSUE-29
ISSUE-30
ISSUE-31
ISSUE-32: Protocol-2015 too vague
ISSUE-33
ISSUE-34: Fault sub-code QName
ISSUE-35: Test cases with wrong delivery mode
ISSUE-36: Test cases with incorrect assertion references
ISSUE-37: Non-fault SOAP 1.2 test cases
ISSUE-38: WSDL 2.0 --> non-normative
ISSUE-39: Protocol 2038 & correlation ID
ISSUE-40: m:MaxTime in example
ISSUE-41: Editors list wrong
ISSUE-42: Abstract needs improvement
ISSUE-43: Unflagged assertion re all props
ISSUE-44: MAY assertion re: props definition
ISSUE-45: jndiContextParameter has unflagged RFC 2119
ISSUE-46: replyToName spurious assertion
ISSUE-47: topicReplyToName unflagged assertions
ISSUE-48: unflagged message body assertions
ISSUE-49: unflagged xml encoding assertion
ISSUE-50: Missing SOAP 1.1 indication
ISSUE-51: redundant assertions about message body
ISSUE-52: bogus RFC 2119 keyword in table describing JMSReplyTo
ISSUE-53: Missing case in transition description
ISSUE-54: Unflagged SHOULD about JMSDeliveryMode
ISSUE-55: redundant statements about one-way MEP
ISSUE-56: Unflagged assertion about @transport value
ISSUE-57: Unflagged assertion about JMS destination
ISSUE-58: References section a big blob
ISSUE-59: Tests for JMSCorrelationID
ISSUE-60: lacking complete WSDL example
ISSUE-61: SOAP samples problems
ISSUE-62: Derek
ISSUE-63: Derek
ISSUE-64: URI encoding explanatory text too restrictive
ISSUE-65: EXI compatibility
ISSUE-66: Test case cleanup
ISSUE-67
ISSUE-68: Bad JMS example
ISSUE-69
ISSUE-70: Derek
Associate to product:
No change
SOAP-JMS Binding specification
SOAP-JMS Test cases
There are 3 open actions.
↓
ID
↓
State
Title
↓
Person
↓
Due Date
Associated with
ACTION-265
open
Apply the changes to the wiki and FAQ
Eric Johnson
2012-01-31
ACTION-266
open
Update the test case document per action 262
Eric Johnson
2012-02-28
ACTION-267
open
Follow up with Yves about the editors note entry.
Eric Johnson
2012-02-28
Add a new action item
. See
all the action items
Chair, Staff Contact
Tracker:
documentation
, (
configuration for this group
), originally developed by
Dean Jackson
, is developed and maintained by the Systems Team <
w3t-sys@w3.org
>.
$Id: open.html,v 1.1 2013-09-16 14:06:33 carine Exp $