Component getServiceDescription() with WSDL imports

Question

How are WSDL imports handled in JBI service descriptions? I was looking through several specifications OASIS and many of the WSDL definitions are broken into several files and use WSDL imports. According to the JBI spec,
"The document must not use the <wsdl:import> or <wsdl:include> elements (the document MUST be stand-alone)."
From this I gather it is up to a JBI component developer to merge existing WSDL specs together so that they can be represented by a WC3 Document object?
Also several of the OASIS specs have WSDL SOAP binding requirements. Since the SOAP binding component is not in the JBI spec is it optional that the binding allow component/SU deployer's to specify the precise bindings to the Services? How does open-esb handle it?

Answer 1

Aaron,
The JBI component developer must do the merge you mentioned. Quite often this is done at design-time, and deployed as part of the service unit, so the component itself has little or nothing to do to create the description.
The JBI specification does require each JBI implemenation to provide a WS-I 1.1-compliant SOAP binding.
A service engine only declares the "service-engine" type of endpoint for services provided; if it declares other endpoint types (say, a SOAP binding) it is meaningless from the JBI perspective.
To expose a service provided by an SE through the SOAP BC, normally an SU must be deployed to the BC (usually part of the SA that contains the SU for the SE).
More dynamic situations are possible: the BC could dynamically discover services, and expose them to external consumers using some sort of heuristic mapping. This dynamic approach remains, as far as I know, theoretical: no one has actually implemented such a BC. Controlling exposure of services is something that needs to be more carefully controlled, via design-time mechanisms and/or a registry/repository.