Project: talendesb
Issue TESB-3278: WSDL Improvement of the SOAP based Service Locator proxy.
As developer I want to use a service that follows the WS-I guidelines and best pratices to ensure interoperability and ease of use. Oliver Wulf did a quick review and has a rather long lists of topics (see below) we should fix. We should also ensure it it conforms to WS-I Basic Profile Version 1.2 (http://www.ws-i.org/Profiles/BasicProfile-1.2-2010-11-09.html) Use the test tools provided to ensure conformance. --- {noformat} Relevant snippets from Olis mail (if you have questions don't hesitate to contact Oliver) ..... - - targetNamespace=http://service.proxy.locator.esb.talend.org/ (way to fine grained) - SLPropertiesType better fit for WS-Addr EPR Metadata - ??? (use parameters as the name) - LocatorProxyService name for portType: this is the interface, not the service - a binding called locahostBinding ??? - , this is the service, why impl suffix - , again, a wsdl port with name localhost (how will it be named if used remotely ;-) - not wrapped doc/literal compliant:	- there is no need for a type definition, only one element is of this type - xmlns:corbatm=http://cxf.apache.org/schemas/cxf/idl/Bank/corba/typemap ??? - xmlns:sl="http://talend.org/esb/serviceLocator/4.2"> - isn't this an implementation detail and shouldn't be part of the contract? - no versioning... do we have any naming guidelines for wsdl/schemas? ... - define some naming guidelines: Adrian and myself put once something together: http://blogs.iona.com/sos/2007/04/design_for_success_best_practi.html (mainly based on guide lines Zurich has in place too) Maybe define something like: http://schemas.talend.org/esb/2011/04/locator http://webservices.talend.org/esb/locator_v1 WSDL Service name: LocatorService_v1_0 {noformat}
Story points: 3