How Project Artifacts are Named
Channel Folders
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:
http://ACME:9090/Service/Trial/getBook
The folder structure would be /Service/Trial
and the channel name would be getBook
.
Destination Names
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:
http://www.acme.com/TNT/webservices/getByteField
Becomes:
http___www_acme_com_TNT_webservices_getByteField
Rules and Rule Functions
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.
You implement the rules and rule functions in your project according to the web service you want to implement.
Events
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
.
Faults
Faults specified in a WSDL are used in the outbound SOAP event, as the Fault element.