SU for component that uses WSDL 1.1 description

I have a component that provides an endpoint described using WSDL 1.1. I also have another component that consumes that endpoint. I would like to define Service Units (SU's) for the components.

According to the JBI deployment descriptor schema the 'provides' and 'consumes' elements in a SU descriptor must have 'interface-name', 'service-name', and 'endpoint-name' children. Since 'interface-name' is a WSDL 2.0 concept, my I use the WSDL 1.1 portname from the endpoint's WSDL?

Are the SU's jbi.xml files used by a JBI container in any way or are they really only there for use by components they are deployed to? Is the validity of the WSDL reference values in a SU's jbi.xml file verified by the JBI implementation?

[753 byte] By [AaronAnderona] at [2007-10-2 17:17:00]
# 1

Yes, the WSDL 1.1 names map straightforwardly to the WSDL 2.0 terminology used in JBI:

interface-name -> tns: portType@name

service-name -> tns: service@name

endpoint-name -> tns: service/port@name

ServiceEndpoint -> tns: service@name, tns: service/port@name

The SU descriptor file is there for tools to allow recomposition of a service assembly without having special knowledge of the contents of each SU type. The descriptor declares static dependencies, so the JBI implementation cannot really use this information for verifying a component's behaviour, since dyanamic dependencies on services (or dynamically provided services) are also allowed.

RonTen-Hovea at 2007-7-13 18:32:38 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...