WSDL 2.0 VS WSDL 1.1

WSDL 2.0

1  1) WSDL 2.0 was designed to solve the interoperability issues found in WSDL 1.0/1.1 by using Improved SOAP v1.2 bindings

2   2) WSDL 2.0 permits fault messages to be declared within the interface element in order to facilitate reuse of faults across operations. If a fault occurs, it terminates whatever message sequence was indicated by the message exchange pattern of the operation,

     3) WSDL2.0 provides Support for additional message patterns (ex:  “Out – Multi In” could correspond to Register for Events, Receive 0-n Events 

     4) WSDL 2.0 Provides Better and more powerful fault handling notation, allowing clearer and easier reuse of WSDL segments within the WSDL file

     5) WSDL2.0 Support for interface inheritance.

      6)      RESTful services

RESTful services can be described fairly with the structure supported by WSDL 2.0. WSDL 2.0 provides a              better model for describing RESTful services than WSDL 1.1

However with WSDL 1.1,

RESTful services could also be defined using WADL (Web Application Description Language.

7) WS-I Basic Profile
            WS-I Basic Profile v1.1 provides guidance for using SOAP 1.1, WSDL 1.1, and UDDI 2.0

            WS-I Basic Profile v2.0 provides guidance for using SOAP 1.2, WSDL 1.1, UDDI 2.0, WS-Addressing, and               MTOM.

8)      Changes from WSDL 1.1 Specification

1)      target Namespace a required attribute of the definitions element in WSDL 2.0

2)      Message constructs are specified using the XML schema type system in the types element in WSDL 2.0

3)      No support for operator overloading in WSDL 2.0

4)      PortTypes renamed to interfaces. Support for interface inheritance is achieved by using the extends attribute in the interface element.

5)      Ports renamed to endpoints




    9) Differences between WSDL1.1 and WSDL 2.0:

tokenize() Usage to split the String in Tibco BW

Tokenize Usage in Tibco


Example

Input String  :  PS00007.ELEM~1,PS00012.ELEM~1

Output Expected
<ns0:POFLine>
<ns0:ProductPartNumber>PS00007.ELEM</ns0:ProductPartNumber>
<ns0:Count>1</ns0:Count>
</ns0:POFLine>
<ns0:POFLine>
<ns0:ProductPartNumber>PS00012.ELEM</ns0:ProductPartNumber>
<ns0:Count>1</ns0:Count>

</ns0:POFLine>

Steps
tib:tokenize($Start/root/param, ',')

output
 PS00007.ELEM~1
 PS00012.ELEM~1

Pass dynamic file URL in document in XSLT

XSLT - How to pass dynamic file URL in document.

<xsl:for-each select="document($fileUrl)/SXXXXX/*/Field">

1) Use Parameter name instead of variable will resolve the issue

2) Pass Absolute path to a variable
    <xsl:variable name="fileLocation" select="'C:/XXX/'"/>

3) Pass Relative Path to a variable
     <xsl:variable name="fileUrl">../staging/<xsl:value-of  select="$producttype"/>.xml</xsl:variable>

Concatenate query values with comma separated with quote IN SQL usage in Tibco SQL Direct

Concatenate query values with comma and quote Separated in Tibco SQL Direct is  passed as IN parameter

concat("'",tib:concat-sequence-format($Start/pfx:GetOrdersByXXXXRequest/pfx:OrderXXX,"','"),"'")