OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-caf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [ws-caf] WS-Context 0.9.2 typo in wsctx.wsdl


I do not think we have an option here.  We *must* fix the problem and 
vote again.

thanx,
    doug

On 04/10/05 12:59, Mark Little wrote:

> Agreed, but can we fix it post adoption or do we have to go through 
> another 15 day period? If there's an option, you know which one gets 
> my vote!
>
> Mark.
>
>
> Greg Pavlik wrote:
>
>> I'm not sure I understand the distinction entirely. The message is 
>> correlated, so from an implementation perspective it's not really 
>> ambiguous at all.
>>
>> Having said that, its clearly a typo that needs to be fixed.
>>
>> Doug Bunting wrote:
>>
>>> Do this error and the history mean the two operations sharing the 
>>> same signature (TimeoutMessage and TimeoutSetMessage) have 
>>> consistently been impossible to distinguish and the 
>>> UserContextServicePortType is ambiguous?  Or, is the 
>>> TimeoutSetMessage "just" unusable?  In other words, what is the 
>>> severity of this problem?
>>>
>>> thanx,
>>>    doug
>>>
>>> On 04/10/05 08:18, kevin.conner@arjuna.com wrote:
>>>
>>>>> Can we clarify whether this is a typo/editors error where the wsdl 
>>>>> is out
>>>>> of sync with the text, or whether the mismatch has gone unnoticed 
>>>>> for some
>>>>> time?
>>>>>   
>>>>
>>>>
>>>>
>>>>
>>>> The file history suggests that the WSDL has always been out of step 
>>>> with
>>>> the document in respect of this message.
>>>>
>>>>    Kev
>>>>
>>>>  
>>>>
>>>
>>


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]