- From: David Orchard <dorchard@bea.com>
- Date: Mon, 7 Nov 2005 14:31:12 -0800
- To: <public-ws-addressing@w3.org>
- Message-ID: <32D5845A745BFB429CBDBADA57CD41AF1439A278@ussjex01.amer.bea.com>
A set of concerns and questions about the QName reference in Marc's proposal. 1. This makes the simple case hard, as a simple protocol switch requires another binding element. 2. Which operations are used for the response binding when it isn't input/output mep? One-way input, one-way output, output followed by input? 3. Which modules/features/properties are used from the selected response binding? Are all the component model properties, such as wsoap:header, "picked up"? 4. What happens if the component model properties "collide" between the "source" and "reference" binding, such as binding#1 and #2 both have wsoap:action specified. 5. What if, any, component model properties are used for the original source binding, including the original response operation? 6. Which of Binding Faults, infaults, outfaults are picked up by the reference? 7. Is it possible to switch out of a SOAP binding? For example, I could point to an HTTP binding for the response which says that the response type is not soap. 8. Can I switch into a SOAP binding? Could I switch from an HTTP binding to a SOAP binding to effectively be a "soap-response mep"? Cheers, Dave
Received on Monday, 7 November 2005 22:31:19 UTC