tibco · 2018. 5. 31. · tibco kabira adapter factory for java release notes viii |tibco product...

TIBCO Kabira® Adapter Factory for JAVA

Release NotesSoftware Release 5.8.3June 2018

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.

ANY SOFTWARE ITEM IDENTIFIED AS THIRD PARTY LIBRARY IS AVAILABLE UNDER SEPARATE SOFTWARE LICENSE TERMS AND IS NOT PART OF A TIBCO PRODUCT. AS SUCH, THESE SOFTWARE ITEMS ARE NOT COVERED BY THE TERMS OF YOUR AGREEMENT WITH TIBCO, INCLUDING ANY TERMS CONCERNING SUPPORT, MAINTENANCE, WARRANTIES, AND INDEMNITIES. DOWNLOAD AND USE THESE ITEMS IS SOLELY AT YOUR OWN DISCRETION AND SUBJECT TO THE LICENSE TERMS APPLICABLE TO THEM. BY PROCEEDING TO DOWNLOAD, INSTALL OR USE ANY OF THESE ITEMS, YOU ACKNOWLEDGE THE FOREGOING DISTINCTIONS BETWEEN THESE ITEMS AND TIBCO PRODUCTS.

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, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO Runtime Agent, TIBCO Administrator, and TIBCO Enterprise Message Service 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 ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2010-2018 TIBCO Software Inc. All rights reserved.

| v

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.8.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.8.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 5.8.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 5.8.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 5.8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 5.8.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 5.8.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Release 5.8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 5.8.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 5.8.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 5.8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

TIBCO Kabira Adapter Factory for JAVA Release Notes

vi | Contents


| vii

Preface

TIBCO Kabira(R) Adapter Factory for JAVA permits to automatically expose a Kabira type to external systems or provides client access to an external object via RMI, RMI-IIOP, or EJB protocol.

Topics

• TIBCO Product Documentation, page viii

• Connecting with TIBCO Resources, page xi


viii | TIBCO Product Documentation

TIBCO Product Documentation

This section lists the documentation resources you may find useful.

The following documents form the TIBCO Kabira documentation set:

• TIBCO Kabira® Adapter Factory for JAVA Installation Read this manual for instructions on site preparation and installation.

• TIBCO Kabira® Adapter Factory for JAVA Release Notes Read this manual for a list of new and changed features, steps for migrating from a previous release, and lists of known issues and closed issues for the release.


Preface | ix

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME Many TIBCO products must be installed within the same home directory. Thisdirectory is referenced in documentation as TIBCO_HOME. The default value ofTIBCO_HOME depends on the operating system. For example, on Unix systems,

the default value is /tibco.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO Fulfillment Catalog Installation and Configuration.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName

Key combinations Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.


x | Typographical Conventions

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use


Preface | xi

Connecting with TIBCO Resources

How to Access All TIBCO DocumentationAfter you join TIBCOmmunity, you can access the documentation for all supported product versions here:

http://docs.tibco.com

How to Contact TIBCO SupportFor 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.


http://www.tibco.com/services/supporthttps://support.tibco.comhttp://docs.tibco.com/TibcoDoc

xii | Connecting with TIBCO Resources


| 1

Release Notes

Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request for one. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 3


https://support.tibco.com

2 | Release Notes

New Features

This section lists the features of this product.

Release 5.8.3JDK Upgrade

TIBCO Kabira Adapter Factory for JAVA now uses JDK 1.8.

Release 5.8.2There are no new features in this release.

Release 5.8.1There are no new features in this release.

Release 5.3The following is the new feature in this release:

• JCA: Inout parameters are not supported.

Release 5.1.1The following is the new feature in this release:

• JAF: Needs support for unsigned type.

Release 5.0The following is the new feature in this release:

• JCA: Add keyword mangling to fields.

• Doc Impact of 031218-000000: SWSRV: Do not start tnamesrv any more.


Changes in Functionality | 3

Changes in Functionality

This section lists changes in functionality since the last release of this product.

Release 5.8.3There are no changes in functionality in this release.




4 | Release Notes

Deprecated and Removed Features

This section describes deprecated features (if any), and lists features, if relevant, that may be useful alternatives to the deprecated features. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the suggested alternative features.

This section also lists features that are removed (if any).

Release 5.8.3No features are deprecated in this release.




Migration and Compatibility | 5

Migration and Compatibility

This section explains the impact of migration from a previous release to this release to various parts of the application.

Release 5.8.3There are no migration procedures or compatibility issues in this release.




6 | Release Notes

Closed Issues

The table in this section lists issues that were closed in the named releases.

Closed in Release Key Summary

5.7.8 CHANNELS-2989

JAF: Update JVM to current versions.

5.4 060922-000002 JAF: incorrect JDK version.

5.3 060116-000015 JCA: mangling problem with “java.lang.InterruptedException”.

5.3 051213-000003 JAF: Java version info in release notes.

5.3 051004-000010 JAF: test result differences between linux and sol.

5.0 050310-000007 JAF: Installing JAF.

5.0 020620-000000 JAF: List of reserved JSA keywords incomplete.

5.0 040715-000010 JAF: jar files incorrectly distributed.

4.2.4 040614-000009 JAF: 4.2.4 release notes.

4.1 030117-000009 ISO8859 character set support for JAF.

4.1 001122-000004 JDK 1.3: tnameserv leaks FDs.

4.1 010804-000001 Java server memory leak.

4.0.5 000520-000000 Java VM: Must set context from current thread.

5.0 041214-000008 JCA: Build fails if a field member shares the name with a method in Java class.

5.0 011002-000007 JCA: java hidden fields cause fatal errors.

5.0 040924-000006 JAF: JCA: Improve robustness of OSJavaObject class.

5.0 030710-000023 JCA: Relative build-time classpaths not converted to absolute paths.

5.0 030508-000016 JCA: enhancement: non-existant .jar in classPath should warn but not terminate.


Closed Issues | 7

5.0 031029-000007 JCA: doesn't support audit.

5.0 021001-000007 JCA: use SWTrace.java to directly trace JavaImporter messages.

5.0 030214-000007 JCA: Mangle hidden java attributes.

4.3 030815-000001 JAF: Mangle of $ doesn't work for arrays.

4.3 030903-000009 JCA: Generated typedefs with inner class syntax ($) don't get mangled.

4.2.4 030815-000001 JAF: mangle of $ doesn't work for arrays.

4.2.4 030903-000009 JCA: generated typedefs with inner class syntax ($) don't get mangled.

4.2 030527-000001 JCA: runtime and generated code mis-using handleException().

4.2 030507-000001 JCA: Build stops with diagnostic missing.

4.2 030414-000014 JCA: build fails to find valid ExceptionHolder.

4.2 030710-000014 HP JAF: QA regression javaComplex inout struct.

4.1 021228-000000 JSA: Fails to exit on failure to connect with name server.

4.0.5 020624-000005 JCA: Have absolute path in classPath configuration value.

4.0.5 000307-000000 JCA: ClassNotFound exception for cosnaming.

4.0.5 020731-000005 JCA: "." in classpath specifications does not work.

4.0.5 000307-000002 JSA: Hang in multi-client stress test.

4.0.4 020610-000005 JCA: JNI code not deleting global object reference.

4.0.3 020521-000002 JCA: invoking wrapped method with argument raises exception.

4.0.2 020415-000002 JCA: Crash marshalling distributed JCA object.

4.0.2 020422-000009 JCA/JSA: Duplicate configuration options.

4.0.2 020422-000001 JCA fails to wrap java classes containing inner classes.

4.0.2 020319-000001 JCA: holder wrapper for java.lang.Throwable missed.



8 | Release Notes

4.0.2 020110-000007 JCA: Propogate class path to XML configuration.

4.0.2 020511-000001 JCA: Exception names not mangled.

4.0.2 020417-000002 CSA: deadlockBackoff called incorrectly (As it is applied to JSA).

4.0.2 020306-000005 Plugins: Remove redundant configuration from service init.

4.0.1 011029-000004 JCA: Generates non-unique alias/attributes.

4.0 010103-000003 JCA: reads user CLASSPATH.

4.0 010123-000006 JCA: wrap: can't give multiple classpaths.

4.0 010306-000021 JCA/JSA: Duplicate JVMMgr configuration info.

4.0 010329-000016 JCA: jclient modeltest lib name clash.

4.0 010717-000003 JCA: Exception generated when returning an Object array.

4.0 010724-000003 JCA: requires a restart for successive builds.

4.0 010802-000009 JCA: fails to get java class objects with the given classpath.

4.0 010814-000006 JCA: Generated interface names not quoted.

4.0 010815-000003 JCA: Overloaded operations (ignored and forgotten).

4.0 020219-000006 JCA: Need definitions for exceptions with no importable methods.

4.0 020226-000020 JCA: mangleKeywords and mangleOverloadedOps problem.

4.0 020215-000003 JCA: codegen problem is mangleUnderscore=TRUE.

4.0 020208-000003 JCA: Createaccess error for methods return interface types from another pkg.

4.0 011207-000002 JCA: Propogate Java exceptions to the DC User.

4.0 010219-000002 JSA: Empty incorrectly mapped to Java object.

4.0 010404-000032 JSA: No documentation on exception mapping.

4.0 010626-000008 JSA: Generated code doesn't trace stack dumps.



Closed Issues | 9

4.0 010807-000013 JSA: Inconsistent transaction handling.

4.0 011126-000003 JSA: RMI / RMI-IIOP does not generate remove method.

4.0 011127-000005 JSA: Deletion of interface with delete access revoked fails.

4.0 011129-000000 JSA: Create of singleton should return the same remote reference.

4.0 011228-000001 JSA: string_to_object is not wrapped in retry loop.

4.0 011116-000002 JSA: Create/destroy methods do not retry.



10 | Release Notes

Known Issues

The table in this section lists known issues in this release.

Change Request ID Summary/Workaround

060905-000004 Summary JAF: segmentation violation on linux x86 platform.

The problem in confined only to linux x86 platform and leads to sporadic SIGSEGV (signal 11) of JAF-enabled engines.

Workaround Use java signal chaining facility. Set and export LD_PRELOAD environment variable before running a JAF-enabled application:

LD_PRELOAD=”$JAVA_HOME/jre/lib/amd64/libjsig.so.

010830-000012 Summary JCA: create with values clause gets assertion.

Attempts to create a JCA imported object with values for the attributes will result in an exception.

Workaround Create the object with no values, and then assign values to the attribute once the object is created.

If there are no default constructor or the attributes are not public, then create a wrapper containing a method which provoides access to the constructor.

011127-000000 Summary COORD: can't kill JCA nicely.

The coordinator is not able to kill the engine gracefully. Engine has to be killed using 'kill -9' as seen in trace log.

Workaround No workaround for this issue is necessary, message is a warning message only.


Known Issues | 11

010109-000009 Summary JCA: Inheritance hierarchy not preserved.

JCA does not preserve the inheritance hierarchy of imported classes. This will cause implicit downcasting to fail in the following example:

interface Parant {} interface Child : Parent {}

interface Test

{

void doIt(in parent);

}

declare Test t;

declare Child c;

//this will fail

test.doIt(child);

Workaround Define the operation's parameter as type Object.

030710-000017 Summary Compiler fatal error in ccfe - stack size exhausted.

When importing many java classes, the Solaris compiler can crash because of stack exhaustion. The compiler cores in ccfe (in this example it is compiling generated com_cdisp.cpp) with the following error:Info] : CC: Fatal error in ccfe: Segmentation Fault (core dumped) dmake: Error code 1, while making 'devobj/com_cdisp.o' dmake: Error code 255, while making 'recursive' [Fatal] : dmake failed.

The stack trace shows:program terminated by signal SEGV (Segmentation Fault) 0x001edc2c: emit+0x000c: st %g1, [%fp - 0x50] (/opt/forte62/SUNWspro/bin/../WS6U2/bin/sparcv9/dbx) where =>[1] emit(), at 0x1edc2c

or:

program terminated by signal SEGV (Segmentation Fault) 0x001ee9e4: visit_binary+0x01bc: st %o2, [%fp - 0xd8] dbx: core file read error: address 0xff3efed0 not in data space.

Workaround Increase the stack size for the shell invoking the build. eg ulimit -s 24000.



12 | Release Notes

CHANNELS-3005

Summary JAF: iiop stub compilation error with JDK 1.6 when two interfaces have the same name.

The model below will fail during compilation of IIOP stubs. Note that the two interfaces have the same name Intf, and that the Intf interface in package b contains an attribute of type a::Intf.package a

{

entity Ent

{

attribute string name;

};

interface Intf

{

attribute string name;

};

expose entity Ent with interface Intf;

};

package b

{

entity Ent

{

attribute a::Intf aIntf;

};

interface Intf

{

attribute a::Intf aIntf;

};

expose entity Ent with interface Intf;

};

Workaround Rename one of the interfaces. This is a limitation in the underlying JDK.



Known Issues | 13

011126-000002 Summary JSA: Java Classes generated for EJB contain empty bodied methods.

Some of the EJB required methods generated by JSA in HomeImpl and Impl have empty bodies. These are:HomeImpl:

public void remove(Object o) { }

public void remove(javax.ejb.Handle o) { }

public javax.ejb.HomeHandle getHomeHandle() { return null; }

public javax.ejb.EJBMetaData getEJBMetaData() { return null; }

Impl:

public javax.ejb.Handle getHandle() { return null; }

public void ejbCreate() {}

public void ejbRemove() {}

public void ejbActivate() {}

public void ejbPassivate() {}

public void ejbLoad() {}

public void ejbStore() {}

public void setEntityContext(EntityContext sc) {}

public void unsetEntityContext() {}

000912-000007 Summary JSA: Return of wchar sequence.

Not properly initialized sequence of "wchar" returned by JSA adapter causes exception in the Java client. IDLos "wchar" is mapped to Java "char". The problem is the result of the restriction that Java places on "char" type that it must be a valid Unicode character, while OS does not impose this restriction on the "wchar" type.

Workaround Ensure that "wchar" in the sequence are initialized to the valid Unicode value.

000725-000004 Summary JSA: Add support for unions.

JSA does not support IDL unions. If an IDL union is used as an attribute, operation parameter or operation return type JSA fails model build.

Workaround Avoid exposing unions to JSA.



14 | Release Notes

030214-000002 Summary JSA: JSA Service can not be build as a separate component for the existing implementation.

There is a problem when building a JSA component that exposes the interfaces of already built component. Consider the following example:

If we build component comp:component comp

{

source comp.soc;

package MyPack;

};

Then expose the package MyPack to Java:

component jsacomp

{

import comp;

adapter java

{

package MyPack;

};

};

We got the following failure:[Fatal] : Component "jsacomp" must contain the package for MyPack. Please add this package to the component.

Workaround Specify individual interfaces, as in following:component jsacomp

{

import comp;

adapter java

{

interface MyPack::Int1;

};

};

and have an empty jsacomp_interface.sdl file in the jsacomp build directory.



Known Issues | 15


TIBCO Kabira® Adapter Factory for JAVAContentsPrefaceTIBCO Product DocumentationTypographical ConventionsConnecting with TIBCO ResourcesHow to Access All TIBCO DocumentationHow to Contact TIBCO Support

Release NotesNew FeaturesRelease 5.8.3Release 5.8.2Release 5.8.1Release 5.3Release 5.1.1Release 5.0

Changes in FunctionalityRelease 5.8.3Release 5.8.2Release 5.8.1

Deprecated and Removed FeaturesRelease 5.8.3Release 5.8.2Release 5.8.1

Migration and CompatibilityRelease 5.8.3Release 5.8.2Release 5.8.1

Closed IssuesKnown Issues

tibco · 2018. 5. 31. · tibco kabira adapter factory for java release notes viii |tibco product...

Documents