Project: talendesb
Issue TESB-9298: Incorrect WSDL client behavior in case SR is down or WSDL not in SR
1.In case of WSDL not in Service Registry or Service Registry down the installed service not obtaining WSDL from Service Registry and switching to "create from class" scenario in initializeServiceModel method of ReflectionServiceFactoryBean so as result we have started service with wrong WSDL. Expected behavior: Information about WSDL not in SR or SR is down in container log and service not started. 2.Additional scope: Merge security stuff in WSDL client with latest commits. Seems part of commits for security implementation for SR WSDL client is losted and should be carefully merged with latest commits.
Story points: 2