1. No category

TIBCO ActiveMatrix® Binding Type for REST
Release Notes
Software Release 3.3.0
January 2015
Two-Second Advantage®
2
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH
EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY
(OR PROVIDE LIMITED ADD-ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE
EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY
OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND
CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED
SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE
CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD
OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE)
OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER
LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE
SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND
YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE
BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws
and treaties. No part of this document may be reproduced in any form without the written
authorization of TIBCO Software Inc.
TIBCO and Two-Second Advantage are either registered trademarks or trademarks of TIBCO Software
Inc. in the United States and/or other countries.
Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise
Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of
Oracle Corporation in the U.S. and other countries.
All other product and company names and marks mentioned in this document are the property of their
respective owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT
ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED
AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE
VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL
ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE
CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO
SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S)
AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR
INDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE,
INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.
Copyright © 2010-2014 TIBCO Software Inc. ALL RIGHTS RESERVED.
TIBCO Software Inc. Confidential Information
TIBCO ActiveMatrix® Binding Type for REST Release Notes
3
Contents
TIBCO Documentation and Support Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
New Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9
Known Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
TIBCO ActiveMatrix® Binding Type for REST Release Notes
4
TIBCO Documentation and Support Services
All TIBCO documentation is available on the TIBCO Documentation site, which can be found here:
https://docs.tibco.com
How to Contact TIBCO Support
For comments or problems with this manual or the software it addresses, contact TIBCO Support as
follows:
●
For an overview of TIBCO Support, and information about getting started with TIBCO Support,
visit this site:
http://www.tibco.com/services/support
●
If you already have a valid maintenance or support contract, visit this site:
https://support.tibco.com
Entry to this site requires a user name and password. If you do not have a user name, you can
request one.
How to Join TIBCOmmunity
TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts. It is a
place to share and access the collective experience of the TIBCO community. TIBCOmmunity offers
forums, blogs, and access to a variety of resources. To register, go to:
http://www.tibcommunity.com
TIBCO ActiveMatrix® Binding Type for REST Release Notes
5
New Features
The following new features have been added to version 3.3.0 of TIBCO ActiveMatrix Binding Type for
REST.
Support for Adding a REST Binding on a Reference
You can invoke REST services by adding a REST binding to a composite reference.
Support for Standard JSON on a Service
Standard JSON is now supported on the service side as the default media type.
Support for Pass Through Mode
In the pass through mode, ActiveMatrix Binding Type for REST behaves like HTTP Binding Type. A
WSDL is auto-generated and can then be configured on the REST binding.
Support for Basic Credential Mapping Policy on a Reference
You can add a Basic Credential Mapping policy on a REST Binding reference.
Support for Basic Client Authentication Policy on a Service
You can add a Basic Client Authentication policy on a REST Binding service.
Support for Context Parameters on a Reference
REST Binding (reference) enables you to send and consume HTTP headers from the REST operation
invocations using context parameters.
TIBCO ActiveMatrix® Binding Type for REST Release Notes
6
Changes in Functionality
The following are changes in functionality in version 3.3.0 of TIBCO ActiveMatrix Binding Type for
REST.
Support for Badgerfish JSON on a Service
To send requests and receive response having Badgerfish JSON in the body, use the "application/
bjson" media-type in "Content-Type" and "Accept" header. In the previous releases, "application/
json" was used.
Default Media Type
The default media type in 3.3.0 is now Standard JSON.
When a project created in TIBCO ActiveMatrix Business Studio 3.2.0 with Badgerfish JSON is
imported into TIBCO ActiveMatrix Business Studio 3.3.0, it is mapped to Standard JSON. This
happens because the default media type for 3.3.0 is different from 3.2.0. You can manually change the
Media Type back to Badgerfish JSON, if required.
TIBCO ActiveMatrix® Binding Type for REST Release Notes
7
Deprecated and Removed Features
No features are deprecated or removed as of version 3.3.0 of TIBCO ActiveMatrix Binding Type for
REST.
TIBCO ActiveMatrix® Binding Type for REST Release Notes
8
Migration and Compatibility
There are no migration procedures or compatibility issues in version 3.3.0 of TIBCO ActiveMatrix
Binding Type for REST.
You cannot install TIBCO ActiveMatrix Binding Type for REST on an earlier version of TIBCO
ActiveMatrix and TIBCO ActiveMatrix Binding Type for REST. See the readme and installation guide
for the software prerequisites.
TIBCO ActiveMatrix® Binding Type for REST Release Notes
9
Closed Issues
The table lists closed issues in version 3.3.0 of TIBCO ActiveMatrix Binding Type for REST.
Key
Summary
RSBT-45
When more than one REST binding was added on a composite service in TIBCO
BusinessStudio, running the project in RAD failed.
TIBCO ActiveMatrix® Binding Type for REST Release Notes
10
Known Issues
The table lists known issues in version 3.3.0 of TIBCO ActiveMatrix Binding Type for REST.
Key
Summary
RSBT-230
Summary: The HTTP Client textbox is not cleaned up after the resource template
is deleted from the Resource Templates folder.
Workaround: None
RSBT-231
Summary: While adding a binding, when the pass through mode is enabled, a note
or warning indicating that any existing WSDL on the component reference is
replaced by the pass through WSDL is not displayed.
Workaround: None
RSBT-346
Summary: Error messages for duplicate resource names or operation names are not
displayed immediately when configuring a REST resource configuration (.rrc) file.
Similarly, the error message does not go away automatically when the duplicate
resource names or operation names are removed.
Workaround: Perform a clean operation.
RSBT-358
Summary: The following data types in a generated XSD do not match the data
types in the JSON payload:
1. unsignedByte mapped to short
2. nonpositiveinteger mapped to float
3. nonnegativeinteger mapped to float
4. unsignedshort mapped to int
5. gYear mapped to short
6. negativeinteger mapped to float
7. unsignedlong mapped to float
8. positiveinteger mapped to float
9. boolean mapped to string
Workaround: Edit the XSD file manually to reflect the correct datatypes.
RSBT-363
Summary: While creating a REST Binding on a promoted service, clicking Next
does not result in any action.
Workaround: Click Finish.
RSBT-368
Summary: In the RRC file, if an operation name begins with a '/', an exception is
thrown.
Workaround: None
TIBCO ActiveMatrix® Binding Type for REST Release Notes
11
Key
Summary
RSBT-371
Summary: When a context parameter is added or edited, the 'Regenerated
message is displayed at the promoted reference.
When you click the message, the mappings are created but the error message does
not disappear.
context parameter mappings'
Workaround: Clean the project.
RSBT-382
Summary: If the RRC file name begins with "xml", an error is thrown while
generating the Java implementation.
Workaround: None
RSBT-391
Summary: After renaming an RRC file through the Process Explorer, the name of
the file is updated in the reference > Bindings tab > Rest Resource Configuration
File link.
Workaround: None
RSBT-398
Summary: A REST Service Binding is updated after an operation is added to a
WSDL.
Workaround: None
RSBT-400
Summary: For a WSDL with the following format, the REST BT service returns a
response in an incorrect format and the REST BT reference cannot parse it.
●
WSDL: The in/out message has a single part as Type referring to a complex
type (which uses reference processing of the request with qualified/unqualified
elements and attributes)
The REST BT service returns a response within tags such as "<xmlinstead of a response element of the XSD.
The REST BT reference cannot parse this response as it expects an XSD element.
fragment>..... </xml-fragment>"
If you call the service directly, message exchange happens successfully. However,
the response is in the following format:
<xml-fragment>
<ord:info>someInfo</ord:info>
<ord:expiresOn>1900</ord:expiresOn>
</xml-fragment>
Workaround: None
RSBT-408
Summary: A Null Pointer Exception is thrown when a Pass Through Mode sample
project is deployed in RAD.
Workaround: Deploy the project in Administrator.
TIBCO ActiveMatrix® Binding Type for REST Release Notes
12
Key
Summary
RSBT-58
Summary: If you upload a DAA that includes TIBCO ActiveMatrix Binding Type
for REST, TIBCO ActiveMatrix Administrator does not check whether HTTP
Connector Resource instances (RIs) exist for HTTP Connectors defined for TIBCO
ActiveMatrix Binding Type for REST. Later, when you attempt to deploy this DAA,
the deployment fails because of the missing RI.
Workaround: Create an HTTP Connector Resource instance in the TIBCO
ActiveMatrix Administrator GUI. While configuring the Binding for REST in
BusinessStudio, the name of the resource instance must match the user-specified
HTTP Connector name.
TIBCO ActiveMatrix® Binding Type for REST Release Notes