Yes - I think this was on the list to ask Jamie. I will send him a note!
Thanks,
Kathryn
Kathryn Breininger
Boeing Library Services
425-965-0182 phone
-----Original Message-----
From: Farrukh S. Najmi [mailto:]
Sent: Tuesday, February 06, 2007 2:35 PM
To: Breininger, Kathryn R
Cc: ebXML Regrep
Subject: Re: [regrep] regrep 1/24/2007: Question on RS Section 3.1
Errata(PublicComment)
Breininger, Kathryn R wrote:
>
> It seems we discussed this before Christmas, and that there was some
> issue with changing a wsdl... Maybe I am thinking of something else...
>
I cannot recall for sure but you may be right. Do you think we should
ask OASIS about rules fixing an obvious copy/paste error like this. I
mean how can a Request message return a response that is a Request
message of same type? Not likely hardly ever - right?
>
>
> Kathryn Breininger
> Boeing Library Services
> 425-965-0182 phone
>
>
>
>
> -----Original Message-----
> From: Farrukh S. Najmi [mailto:]
> Sent: Tuesday, February 06, 2007 1:17 PM
> To: Stojanovic, Nikola
> Cc: ebXML Regrep
> Subject: Re: [regrep] regrep 1/24/2007: Question on RS Section 3.1
> Errata(PublicComment)
>
> Stojanovic, Nikola wrote:
>
>> I've discovered one more issue a few hours ago that I think could be
>> a
>>
>
>
>> candidate for errata as it might've been a copy/paste error in the
>> ebXMLRegistryInterfaces.wsdl file. Here is the current snippet from
>> that
>> file:
>>
>> <operation name="updateObjects">
>> <input message="tns:msgUpdateObjectsRequest"/>
>> <output message="tns:msgUpdateObjectsRequest"/>
>> </operation>
>>
>> and it should look like:
>>
>> <operation name="updateObjects">
>> <input message="tns:msgUpdateObjectsRequest"/>
>> <output message="tns:msgRegistryResponse"/>
>> </operation>
>>
>>
>>
>>
>
>
> Yes this is definitely a cut/paste error that did not get noticed. I
> suggest we fix this as now. Thanks.
>
> --
> Regards,
> Farrukh
>
> Web: http://www.wellfleetsoftware.com
>
>
>
--
Regards,
Farrukh
Web: http://www.wellfleetsoftware.com
