![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |
The table following this example shows which WSDL elements and attributes are used to create TIBCO BusinessEvents project artifacts. Elements and attributes used in the import are highlighted in bold text. Differences between import from abstract and concrete WSDL files are also highlighted. See Table 18, Imported WSDL Project Artifacts for more details.
<wsdl:definitions omitted to keep the example short><xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns="http://www.books.org" elementFormDefault="qualified" attributeFormDefault="unqualified" targetNamespace="http://www.books.org">. . . . . . Elements omitted. . . . . . Elements omittedNote: In an abstract WSDL the following elements are used in the import. However in a concrete WSDL, the <wsdl:binding> elements are used instead.Note: This is a concrete WSDL example, so the <wsdl:binding> elements are used in the import. (In an abstract WSDL, the <wsdl:portType> element contents are used instead.)
Table 18 Imported WSDL Project Artifacts For abstract WSDLS: <wsdl:service> is not present, so the folder structure starts from the folder created from <wsdl:portType>. For abstract WSDLs, in <wsdl:portType> section.For concrete WSDLs, in <wsdl:binding> section. For abstract WSDLs, in <wsdl:portType> section.For concrete WSDLs, in <wsdl:binding> section. For abstract WSDLs, in <wsdl:portType> section.For concrete WSDLs, in <wsdl:binding> section. For abstract WSDLs, in <wsdl:portType> section.For concrete WSDLs, in <wsdl:binding> section. If the import is from a concrete WSDL, the HTTP Connection resource, Channel resource and Destination resource are added using details in the <wsdl:service> section of the WSDL. The host and port come from the <soap:address location> Given a concrete WSDL, folders are created for all the elements after the port, up to the last forward slash of the location URL. The text after the last forward slash is the channel name. For example, given the following location URL:In a concrete WSDL, the SOAPAction attribute of a <soap:operation> element specifies the URL of a destination. It also becomes the destination name. Forward slashes (/), colons (:), and periods (.) are converted to underscore characters (_) to form the name. For example:For each operation, the import utility creates a rule and a rule function. The rule has no body. The rule functions have SoapEventOut as the return type. Null value is returned by default.For example, the GetBook operation becomes a GetBook rule in the GetBookPortType folder which is in the Rules folder, and also a GetBook rule function in the Rulefunctions folder.The <wsdl:input> element becomes a request event and the <wsdl:output> element becomes a response event. Each event type inherits from the SoapEvent event type.Event names come from the message attributes. In the example, the request event is GetBookRequestMessage and the response event is GetBookResponseMessage.
![]() |
Copyright © TIBCO Software Inc. All Rights Reserved |