Re: [ekmi] WSDL files for the SOAP Binding

[Tomas Gustavsson <tomas@primekey.se>]

Hi,

example.com sounds good to me. It doesn't affect the wsdl, as a client
API, as you say.

Regards,
Tomas


Stefan Drees wrote:
> Hi Anil,
> 
> Anil Saldhana schrieb:
>> Hi Stefan,
>>   implementers are discouraged from updating the spec artifacts such
>> as schemas. Toward this, if we include a WSDL as part of the
>> specification similar to schema, I think the requirement is that
>> implementers should not need to make changes.
> 
> that is why I left lurking mode, I mean the "... include a WSDL as part
> of the specification similar to schema ..." ;-)
> 
> In the DSS-X TC (where I have the pleisure to serve as co-chair) we see
> the offering of a WSDL-file more as kind of a supportive service.
> 
> I personally think, that someone setting up a WSDL file for a service,
> often has very specific needs, adding this and that, at least
> "localizing" it.
> 
> The nice thing about "example.com"-ing the location attribute of the
> WSDL soap:address element is, that it is as clear as possible in stating
> the necessity, to fill something sensefull in.
> 
>>
>> The only place where we cannot have anything generic is the location
>> of the soap address. So an implementer has to make changes.  Maybe we
>> can use the "example.com" url and mention in the spec that the
>> implementer is free to change that url.
>>
>> Again, this brings up another question. If the implementer wants to
>> add more information to the wsdl such as ws-policy etc, then ....
> 
> Never the less, a useful supporting document/template ... only, a bit
> less read-only when compared to the schema.
> 
> All the best,
> Stefan Drees.
> 
>> Regards,
>> Anil
>>
>> On 10/20/2009 10:20 AM, Stefan Drees wrote:
>>> Anil,
>>>
>>> Anil Saldhana schrieb:
>>>> For including the WSDL as part of the spec, I am unsure how to
>>>> handle the "soap:address location" which would indicate the location
>>>> of the EKMI service, in a spec generic way.
>>>>
>>>> An example would be something like:
>>>> =========
>>>> <port name="EkmiWSPort" binding="tns:EkmiWSPortBinding">
>>>> <soap:address location="http://myservice/EkmiWSService";></soap:address>
>>>> </port>
>>>> ==============
>>>>
>>>> So we allow the implementers to update the location in the WSDL?
>>>
>>> I always had the impression, that WSDL is very specific and tailored
>>> as a binding description to fit both sides with one being al possible
>>> services realizing the other (Ekmi-Standard).
>>>
>>> Isn't example.com the classic convention to name such an endpoint?
>>>
>>> Hope this helps,
>>> Stefan Drees.
>>>
>>>>
>>>> On 10/20/2009 07:10 AM, Tomas Gustavsson wrote:
>>>>> Everything is in
>>>>> http://download.primekey.se/~tomas/download/WSTest2.zip
>>>>>
>>>>> The wsdl is in the src directory.
>>>>>
>>>>> /Tomas
>>>>>
>>>>>
>>>>> Anil Saldhana wrote:
>>>>>> Tomas,
>>>>>>    can you please attach the WSDL files that you generated to be
>>>>>> included
>>>>>> in the SOAP Binding?
>>>>>>
>>>>>> Regards,
>>>>>> Anil
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php