Lou Amodeo wrote:
Hi, It doesnt appear that Tuscany is implementing section 2.3.2 of the WS
Binding specification completely. Can you explain the
algorithm used for reference and service side WSDL TNS generation for
service, ports, and bindings. Thanks.
The target namespace of the WSDL document, and of the service, ports and
generated binding
272 elements is:
273 Base System URI for HTTP / Component Name / Service Name
I am in the process of changing the Tuscany WSDL generation for the
"WSDL-less" case from using Axis2 to using code within Tuscany.
This will enable SCA-specific customizations of the generated WSDL
(like the rule above) to be incoporated in the WSDL generation
algorithm.
On the service side, in the absence of JAX-WS customizations, it
seems clear that Tuscany should use the above algorithm to calculate
the TNS. If JAX-WS customizations are specified, I believe Tuscany
should use them to override this default. It would be good to get
a spec clarification that this is correct.
On the reference side, the information stated above may not be
available. If there is an @target on the reference, it would be
possible to use the target's component and service. However, this
information isn't available if there's no @target. The spec should
state what the reference side should do in the cases with and
without @target specified.
I'll open a spec issue to clarify what should happen in all these
cases. Until this is resolved, I'm inclined to leave the new
WSDL generation code for references as it stands currently,
i.e., using the TNS specified by JAX-WS.
Simon
