Why are some services missing the wsdl:service definition?

[RobinGoussey]

Hi,

I am trying to generate java code to implement all the wsdls, but they only generated the interface, and not the service/implementation. After some digging, it is because some of the wsdl's no longer define a service. I needed to manually add:

	<wsdl:service name="MediaService">
		<wsdl:port name="MediaPort" binding="trt:MediaBinding">
			<soap:address location="http://www.onvif.org/ver10/media/wsdl"/>
		</wsdl:port>
	</wsdl:service>

Any specific reason they are no longer present? Or we're they never present and did the library add them?

[steven93921]

Hi Robin,
Java (wsimport) is one of the few (maybe the only) parsers that required the service to be defined. The ONVIF WSDL files never provided the service definition. Since ONVIF is only specifying the interface, this makes sense to leave it up to each individual implementation how to provide those services. I always defined the service either directly in the ONVIF WSDL file or creating a parent WSDL file that imported the ONVIF WSDLs and defined all the services I needed to generate. I recommend the latter as it is easier when ONVIF publishes updates to the WSDL file you don't need to keep re-adding the service.

-Steven

[svefredrik]

Python client (suds) also requires service definition

[HansBusch]

We had service definitions in the very first release back in 2008. They resulted in some stubs automatically connecting to the provided URL.

[HansBusch]

I like Steve's suggestion with the master service wsdl. I'm not sure whether it makes sense for ONVIF to maintain such a master file since applications may typically do not want to import all wsdl files ONVIF has defined at once.