Re: [ekmi] WSDL files for the SOAP Binding

[Anil Saldhana <Anil.Saldhana@redhat.com>]

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.

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 ....

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