tibco adapter™ for ejb - tibco product documentation · pdf file† jboss 3.2.3...

TIBCO Adapter™ for EJB

Release NotesSoftware Release 5.3.0December 2006

Important InformationSOME 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 TIBCO ADAPTER FOR EJB USER’S GUIDE). 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.

TIB, TIBCO, TIBCO Software, TIBCO Adapter, Predictive Business, Information Bus, The Power of Now, TIBCO Designer, TIBCO ActiveEnterprise, TIBCO Administrator, TIBCO Hawk, and TIBCO Enterprise are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.

EJB, J2EE, JMS and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. 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. PLEASE SEE THE README.TXT 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 © 1999-2006 TIBCO Software Inc. ALL RIGHTS RESERVED.

TIBCO Software Inc. Confidential Information

| iii

Contents

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

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Deprecated Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Compatibility and Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Related Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

TIBCO Adapter for EJB Release Notes

iv | Contents


| 1

Release Notes

Check the TIBCO Product Support web site at http://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 one from the same site. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 8

• Deprecated Features, page 13

• Compatibility and Migration, page 14

• Related Release Notes, page 15

• Closed Issues, page 16

• Known Issues, page 22


2 | Release Notes

New Features

This section lists new features added since the last major release of this product.

Introduced in Release Feature

5.3.0 Implementation of JCA 1.5 Specification

This release of the adapter implements J2EE Connector architecture (JCA) 1.5 specification. The JCA 1.5 connector is bi-directional.

5.3.0 Added Platform Support

This release of the adapter provides support for the following platforms:

• HP-UX 11i V2 (Itanium)

• Red Hat Linux 4.0 (x86)

• AIX 5.3 (POWER)

5.3.0 Added Application Server Support

Support for the following application servers has been added:

• BEA WebLogic Application Server 7.0 with SP7

• BEA WebLogic Application Server 8.1 with SP5 and SP6

• BEA WebLogic Application Server 9.1 and 9.2

• IBM WebSphere 6.1

• JBoss Application Server 4.0.3 and 4.0.4

• Oracle 10g Application Server 10.1.3

5.3.0 Support for Deploying the Connector as an EAR File

Scripts are provided to build and deploy the EAR file. However, this feature is currently supported only for the following application servers:

• JBoss Application Server 4.0.3 and 4.0.4

• BEA WebLogic Application Server 9.1 and 9.2



New Features | 3




• BEA WebLogic Application Server 9.0

• IBM WebSphere 6.0 and 6.0.2

5.2.0 Support for Clustered Environment

Support for deploying a connector in clustered environments has been added for IBM WebSphere Application Server 6.0.

5.2.0 Support for Multiple Application Servers

This feature provides the flexibility of installing the adapter without selecting any application server, so that the adapter services can later be configured to connect to different application servers if required.

However, configuring adapter services in a single adapter instance to connect to different versions of the same application servers is not recommended.

An adapter instance where the service(s) are connecting to the IBM WebSphere application server as well as to other application servers is also not recommended.

5.2.0 Support for Deploying the Connector as an EAR File

There are scripts provided to build and deploy the EAR file. However, this feature is currently supported only for the following application servers:



• JBoss Application Server 4.0.0, 4.0.1 and 4.0.2.

• IBM WebSphere 5.0, 5.0.2, 5.1, 6.0 and 6.0.2

5.1.2 Support for Clustered Environment

Support for deploying a connector in clustered environments has been added for BEA WebLogic Application Server 8.1.



4 | Release Notes



• JBoss 4.0.0, 4.0.1 and 4.0.2

• BEA WebLogic 8.1 with SP3 and SP4

• Oracle 10g 9.0.4, 10.1.2

• Sun Java System Application Server Platform Edition 8.1


Support for the following platforms has been added:

• IBM AIX 5.2

• Red Hat Linux AS 3.0



• JBoss 3.2.3

• BEA WebLogic 7.0 with SP5

• BEA WebLogic 8.1 with SP2


5.1.1 Remote Deployment Information Available in User’s Guide

Information for remote deployment is now available in the TIBCO Adapter for EJB 5.1.1 User’s Guide.


Support for the following platforms has been added:

• Microsoft Windows Server 2003

• Solaris 9




New Features | 5



• IBM WebSphere Application Server 5.0.2


• JBoss 3.2.1

5.1.0 Support for TIBCO BusinessWorks 5.1

The adapter can be used in a TIBCO BusinessWorks 5.1 process.

5.1.0 TIBCO BusinessWorks Examples

TIBCO BusinessWorks examples are provided as part of the adapter installation to demonstrate common business scenarios.

5.1.0 Support for TIBCO Administrator 5.1.2

The adapter is compliant with TIBCO Administrator 5.1.2.

5.0.1 Support for Additional Application Servers

This release of the adapter provides support for the following:

• IBM WebSphere Application Servers 4.0.3, 4.0.4, and 5.0

• Java 2 Platform, Enterprise Edition Application Server 1.3.1

• JBoss Application Server 3.0.4

• Oracle9i Application Server 9.0.3

• Sun Java System Application Server Platform Edition 7

• BEA WebLogic Application Server 6.1 and BEA WebLogic Application Server 6.1 with SP1, SP2, or SP3

• BEA WebLogic Application Server 7.0 and BEA WebLogic Application Server 7.0 with SP2 and SP4



• Microsoft Windows XP Professional with Service Pack 1a

• Red Hat Linux 7.2



6 | Release Notes

5.0.1 Easy-to-use GUI

The adapter now provides an easy-to-use, intuitive GUI for configuring the adapter through TIBCO Designer. Additionally, the code generator tool has been integrated with the GUI.

5.0.1 Support for Internationalization

The adapter provides support for many encodings. For more information on supported encodings, see the TIBCO Adapter for EJB User’s Guide.

5.0.1 Support for JMS Transport

In previous releases, an adapter service could use only the TIBCO Rendezvous transport. In this release, the JMS (Java Messaging Service) transport is also available. An adapter service that uses the JMS transport can communicate only with the TIBCO Enterprise for JMS server.

5.0.1 Support for the XML Wire Format

The XML wire format is supported for the JMS transport.

5.0.1 Support for Multi-file Format Projects

TIBCO Designer 5.0 now allows you to save adapter projects in multi-file format at design-time. This format is useful if multiple adapter configurations are defined in the same project and worked on by several developers. The adapter configuration files can be managed by a version control system.

5.0.1 Standard Connection Management

All adapters now use the same mechanism to handle connection loss to the vendor application.

5.0.1 Standard Error Management

All adapters now use the same mechanism to report errors. Error messages provide more detail, are contextual and can be applied uniformly across adapters. Low-level exception messages like system and TIBCO Rendezvous messages now have appropriate adapter-level information. The error message descriptions and resolutions are documented in the TIBCO Adapter for EJB User’s Guide.



New Features | 7

5.0.1 New Installer

The new installer program has three modes available for installation: GUI, console, and silent. The GUI mode presents panels that allow you to make choices about product selection, product location, and so on. The console mode allows you to make installation choices from the command line. The silent mode either installs using the default settings or uses a response file that was saved during an earlier installation.

5.0.1 TIBCO Hawk Microagent

In addition to the standard microagents that are available with any TIBCO ActiveEnterprise-compliant adapter, the adapter provides its own microagent. In this release, this microagent provides methods for getting basic processing-related statistics, such as getActivityStatistics(), getActivityStatisticsByService(), getActivityStatisticsBySchema(), and resetActivityStatistics().



8 | Release Notes

Changes in Functionality

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

Changed in Release Functionality

5.3.0 Dropped Application Server Support

Support for the following application servers has been dropped:

• BEA WebLogic 6.0

• BEA WebLogic 6.1

• BEA WebLogic 6.1 with SP1, SP2, SP3, SP4, SP5, SP6, and SP7


• IBM WebSphere 5.0.2


5.3.0 Dropped Platform Support

Support for the following platforms has been dropped:

• Solaris 7



Support for the IBM WebSphere 4.0.3 and 4.0.4 application servers has been dropped.


Changes in Functionality | 9

5.2.0 Installer Changes

The following changes are made to the installer:

• A new folder called xdoclet has been added to the adapter installation. The xdoclet folder contains the lib folder. The lib folder contains the xdoclet libraries that are required for automatic generation of deployment descriptors. These libraries are used by the ant scripts to generate and deploy the connector as an EAR file.

• The custom installation option now offers the choice to install the adapter for multiple application servers.

• When the adapter is installed for multiple application servers, <ADEJB_HOME>/lib contains a folder called connectors which stores the AeConnector.rar file for each supported application server.

• The Application Server Connection resource for the adapter palette is only displayed if the adapter is being installed for multiple application servers.

5.1.2 There were no changes in functionality in this release.


Support for the JBoss 3.2.1 application server has been removed.


Support for the JBoss 3.0.4 application server has been removed.

5.1.0 Dropped Platform Support

The following platforms are no longer supported:

• Solaris 2.6

• Red Hat Linux 7.2



10 | Release Notes

5.1.0 Changed TIBCO Hawk Methods

The following TIBCO Hawk methods have changed parameters and are now available in the adapter’s class microagent.

• getActivityStatistics()

• getActivityStatisticsBySchema()

• getActivityStatisticsByService()

The following parameters for the above methods are new or have changed (where applicable). In addition, the parameter order for some of the above methods has changed.

• The new output parameter MeasurementInterval displays the time (in seconds) since the last time the adapter was reset, or if never reset, since the adapter started.

• The Total, Success, and Failure output parameters type has changed from string to integer.

• The new output parameter LineIndex is used as an index for the method. Its value is a concatenated string of the Operation and ServiceName parameters separated by a comma.

5.1.0 TIBCO Rendezvous TX No Longer Supported

The TIBCO Rendezvous Transactional quality of service option is no longer supported. The option is still available in the adapter’s palette for backward compatibility with previous adapter releases.



Changes in Functionality | 11


The following changes have been made to the installer:

• The adapter installation has a new folder called hotfix. The hotfix folder has two subfolders called lib and bin. Hotfix patches are placed in these subfolders.

• All paths in the tra file will be prepended with <ADEJB_HOME>/hotfix/lib and <ADEJB_HOME>/hotfix/bin followed by <ADEJB_HOME>/lib and <ADEJB_HOME>/bin.

• TIBCO software can be uninstalled using the TIBCO Installation Manager program. The TIBCO Installation Manager displays all TIBCO software installed on your machine. Click the Uninstall button to remove the selected product. Note that some products cannot be installed from the utility. Instructions about uninstalling these products are listed in the uninstall window (after clicking the Uninstall button).

5.0.1 Support for Returning ActiveEnterprise Classes from EJBs

An EJB that contains TIBCO ActiveEnterprise functionality can now return an ActiveEnterprise class type to the request-response server service of the adapter. The adapter correctly interprets the returned data and passes it to the request-response invocation client.

5.0.1 Code Generator

The code generator is now integrated into the adapter palette in TIBCO Designer and is no longer available as a standalone application. The code generator generates bean code for endpoints configured with the JMS wire format and has enhanced exception handling abilities. In addition to generating EJB classes for the target ActiveEnterprise schema class, it now generates bean, home, and remote interfaces for all the super classes in that class’ inheritance hierarchy.



12 | Release Notes


Support for the following application servers are not available in this release:

• HP Bluestone 7.3

• HP Application Server 8.0

• BEA WebLogic 5.1 and 6.0

• IBM WebSphere 3.5.4

• Java 2 SDK Enterprise Edition 1.3.0

The WebLogic 5.1 and WebLogic 6.0, and WebSphere 3.5.4 application servers are no longer supported by the vendors.

5.0.1 RVCM Handling

Previously, when the adapter was configured to use the TIBCO Rendezvous transport and Certified quality of service, the adapter immediately acknowledged every incoming message on receipt of the message.

The functionality has now been enhanced to acknowledge the incoming message only after the adapter has invoked the method in the target bean in the application server.

5.0.1 Repository Server

The repository server is now a component of TIBCO Administrator. Access control to the repository server can be set using TIBCO Administrator.


The adapter installation program no longer includes the TIBCO Runtime Agent software, which is required by the adapter. This software must be installed prior to installing the adapter.

In previous releases, TIBCO software could be uninstalled using the TIBCO Uninstaller program. In this release, each software component is uninstalled separately by navigating to the _uninst folder and running the Tibuninstall utility.



Deprecated Features | 13

Deprecated Features

This section describes deprecated features and lists equivalent features that accomplish the same result, if relevant. 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 equivalent feature.

Deprecated in Release Feature

5.3.0 No features are deprecated in this release.




5.1.0 Deprecated feature The following 5.0.1 and earlier TIBCO Hawk methods available in the adapter’s custom microagent have been deprecated:

• getActivityStatistics()

• getActivityStatisticsBySchema()

• getActivityStatisticsByService()

• resetActivityStatistics()

Equivalent functionality

The above methods are now available in the adapter’s class microagent and have been enhanced (as described in Changes in Functionality on page 8).

If you use TIBCO Designer 5.1 to modify a 5.0 or earlier adapter configuration for use with a 5.0 or earlier run-time adapter, you must use the methods in the custom microagent, not the methods in the class microagent.



14 | Release Notes

Compatibility and Migration

This section provides information on adapter’s compatibility with and its data migration support for other TIBCO applications.

For information on adapter’s compatibility with TIBCO Runtime Agent and other TIBCO applications, see TIBCO Adapter for EJB readme.txt.

For information on migrating to a newer version of TIBCO Runtime Agent (TRA), see the TIBCO Runtime Agent documentation set. For example, if you need information on migrating to TIBCO Runtime Agent 5.4.0, see TIBCO Runtime Agent Upgrading to Release 5.4.

Make a copy of the project you are migrating to TIBCO Designer 5.x before starting the migration process.

• Migrate 4.x repositories before using them in TIBCO Designer 5.1. Use the migration tool provided with the adapter to migrate 4.x repositories to TIBCO Designer 5.x. For details on using this tool, see Migrating a 4.x Repository for Use with TIBCO Designer 5.x in the TIBCO Adapter for EJB User’s Guide.

• Users upgrading from version 5.1.1 or higher should simply open their previous projects with this new version of the adapter.


Related Release Notes | 15

Related Release Notes

Adapters are supported by infrastructure products from TIBCO. See the following release notes for information about open and closed issues that may affect the adapter.

• TIBCO Designer release notes are available in:

<install-path>\tibco\designer\<version number>\doc\

• TIBCO BusinessWorks release notes are available in:

<install-path>\tibco\bw\<version number>\doc\

• TIBCO Runtime Agent release notes are available in:

<install-path>\tibco\tra\<version number>\doc\

• TIBCO Administrator release notes are available in:

<install-path>\tibco\admin\<version number>\doc\

• TIBCO Enterprise Message Service release notes are available in:

<install-path>\tibco\ems\<version number>\doc\


16 | Release Notes

Closed Issues

This section lists product defects that were closed in the named release.

Closed in Release Defect # Summary

General

5.3.0 1-755OHQ When the JCA 1.0-compliant adapter was undeployed, its outbound instances did not release TIBCO Rendevous sessions or delete them from the application server.

This has been fixed. For the fix to work, use JCA 1.5-compliant TIBCO Adapter for EJB 5.3.0 and TIBCO Runtime Agent 5.3.2 or above.

5.3.0 1-70C15H The adapter could not be stopped from Windows Services Control Panel.

This has been fixed.

5.3.0 1-2ZVSNL If an operation returned an exception class that had no attributes but was derived from a class that had attributes, the adapter displayed the error ATExceptionSUB10.

This has been fixed. The adapter can now handle an exception class with no attributes, provided any one of its parent classes has some attributes.

5.3.0 1-6YL44Y Adapter process was not terminated after sending a message on adapter termination subject. No trace log was generated for internal shutdown.


5.3.0 1-6WJVIE Multiple outbound instances of the connecter could not be deployed on a single application server.


5.1.2 1-1EGIAH The publication and request-response invocation services were not supporting the use of the HTTPS protocol for communicating with the repository, for the following application servers:


• Sun Java System Application Server Platform Edition 7



Closed Issues | 17

5.1.2 1-1Z50RX When a 4.x repository with adapter services was imported into TIBCO Designer 5.x, all end-points were placed under DefaultRVSession instead of the sessions they were configured under. For example, if a request-response service was configured under a session RV1, migrating the repository created a session RV1 with all its configured values, but it was not attached to any endpoint. Instead, a session called DefaultRVSession was created with a default configuration, and the end-points were attached to this session. This was leading to a loss of session information.


5.1.2 1-223R26 The RPC server was not returning the system exceptions to the calling process.


5.1.2 1-223R2I RPC operations with the void return type were not supported.


5.1.2 1-207YJ9 It was not possible to override global variables for the connector configuration through the properties file.


5.1.2 1-39DKOH A complex data structure containing the sequence attribute was getting converted to MappedRecord instead of the Java object.


5.1.1 1-1U6I1N During silent installation of the adapter that used a user-specified response file, the installer ignored some entries in the response file. This prevented the adapter from starting up.


5.1.1 1-1Y0OMF On Linux, when a log file was not specified in the adapter's properties file, the adapter incorrectly created a log file called <java.io.tmpdir>adejb.log instead of <java.io.tmpdir>/adejb.log.




18 | Release Notes

5.1.0 1-12G6BT When an attempt was made to deploy the connector in the BEA WebLogic 8.1 application server, the following error was displayed in the application server console or log, and the connector did not get deployed:

javax.management.MalformedObjectNameException: ObjectName:

Invalid value -> TIBCO Connector Copr. 2000, 2001 TIBCO

Software Inc._tibco/aeconnectorJNDINAME_Pool_1

This was because a tag called <vendor-name> in the connector’s deployment descriptor (ra.xml) contained special characters that were invalid in WebLogic 8.1.

This has been fixed for the WebLogic 8.1 and 8.1 with SP1 application servers. The special characters have been removed from the connector’s deployment descriptor.

5.1.0 1-153RBM The invocation time-out value for the request-response invocation service could not be specified at runtime through the InteractionSpec. Instead, the connector always used the invocation time-out value configured in the repository.

This has been fixed. When the time-out is specified through the InteractionSpec, it overrides the invocation time-out value configured in the repository.

5.1.0 1-XL6SD The TIBCO Enterprise for JMS server showed memory growth when the adapter received a large number of request-response server requests over the JMS transport.


5.1.0 1-XXMS5 When the TIBCO Rendezvous transport was used with the XML Message wire format, only Latin-1 data, such as English and Western European languages, were supported. Other languages, such as Japanese, were not supported when using the TIBCO Rendezvous transport with the XML Message wire format.


5.1.0 1-Y86KD Using the adapter with a large number of RPC method invocation requests over the JMS transport used, led to the growth of the adapter memory usage over time.




Closed Issues | 19

5.1.0 1-YEG3T The publication and request-response invocation services did not support the use of the HTTPS protocol for communicating with the repository.

This has been fixed for use with the following application servers:

• BEA WebLogic Application Server 6.1 and BEA WebLogic Application Server 6.1 with SP1, SP2, or SP3

• BEA WebLogic Application Server 7.0 and BEA WebLogic Application Server 7.0 with SP2 or SP4

• BEA WebLogic Application Server 8.1 and BEA WebLogic Application Server 8.1 with SP1

• IBM WebSphere Application Server 5.0

5.0.1 1-CX5H2 During installation, if an incorrect path or file name was specified for the JVM library, the installer displayed a message that the entry was incorrect, and would proceed with the installation using the incorrect entry.

This has been fixed. The installation will not proceed if the specified path and name of the JVM library are incorrect.

Code Generator

5.2.0 1-5KIVPM The code generator did not provide the correct error message if the return type was empty for an operation class.


5.2.0 1-5KIVRQ While configuring the operation schema for a one-way operation, if the return type was not specified, the code generator was displaying an error.

This has been fixed. For a one-way operation, if the return type is empty, the code generator picks void as the default return type.

5.2.0 1-623KBV For base classes and super classes that were in different folders, the code generator was not generating the package names in the comments of the bean home interface java file.




20 | Release Notes

5.2.0 1-6PHEG4 In TIBCO Adapter for EJB 5.1.2 HotFix1, it was not possible to use the beans generated by the previous versions of the adapter when the connector was deployed as a JAR file instead of a RAR file.


5.1.2 1-1H20P2 The code generator was not creating the code properly for the classes in different schema folders.


5.1.2 1-40WB1D The configured values for an adapter instance were getting lost when the Show All Tabs check box was selected.


5.1.1 1-1D8HN9 The bean code generated by the code generator for the TIBCO AEUnion data type did not pass the correct data to the target bean in the application server.


5.1.1 1-1QRY1E The bean code generated by the adapter in the 5.1.0 release was not backward compatible with 4.1.0. This was because, for the same ActiveEnterprise schema class, the package names of the Java classes generated by the 4.x and 5.x versions of the code generator were different. For example, for an ActiveEnterprise schema class A, in a folder Test directly under the Classes folder,

• The 4.x version used the package name <user_specified_package_name>/Test

• The 5.x version used the package name <user_specified_package_name>/Test/AeSchemas/Test

This has been fixed. The package names used by the 5.1.1 code generator are now the same as those used by the 4.x code generator.

5.1.1 1-1ZQA45 The code generator failed for request-response and request-response invocation services, if the operation class associated with the service and the return type from the operation were in the same folder.




Closed Issues | 21

5.1.0 1-134EHQ When ActiveEnterprise schema class definitions and declarations for sequences were not created in the same folder, the code generator was unable to generate the code for these sequences.


5.1.0 1-2H18X, 1-5Y85R

If the code generator encountered ActiveEnterprise schema names that were reserved J2EE words or TIBCO class and package names, it would generate bean code with invalid Java names containing the reserved words. The generated bean code could not be compiled out-of-the-box. For such cases, the generated Java code for classes, operations, parameters, exceptions, scalars, and complex types had to be modified before it could be compiled successfully.

This has been fixed. When generating the bean code, the code generator converts every reserved J2EE word and TIBCO class and package name it finds in the schema, into a valid Java name using a predefined mapping table. You can find details of this mapping in Appendix D of the TIBCO Adapter for EJB User's Guide.

5.1.0 1-5Y862, 1-XPK71

The code generator did not generate bean code that could be compiled out-of-the-box, if the ActiveEnterprise schema in the repository contained names embedded with special characters. For such cases, the code generator would generate Java code for classes, operations, parameters, exceptions, scalars, and complex types that would contain these special characters, which had to be modified before the code could be compiled successfully.

This has been fixed. When generating the bean code, the code generator converts every special character it finds in the schema, into a valid Java name using a predefined mapping table. You can find details of this mapping in Appendix D of the TIBCO Adapter for EJB User’s Guide.

5.0.1 1-5YGEL The code generator tool did not generate the EJB code for endpoints configured with the TIBCO Rendezvous transport and the Certified quality of service.


5.0.1 1-6KGTH If the code generator encountered multiple ActiveEnterprise operations in the schema whose exception classes had the same name, the code generator displayed an error and did not generate the code.

This has been fixed. You can now use similar exception names across multiple operations.



22 | Release Notes

Known Issues

The table in this section lists product defects known in this release.

Defect # Summary/Workaround

General

1-19YVXS Summary Latin-1 message encoding is not supported for the JMS and TIBCO Rendezvous transports when configured to use the XML message wire format.

Workaround To use the XML message wire format, the default message encoding, Latin-1 (ISO8859-1) must be changed to UTF-8. Otherwise, use the TIBCO Rendezvous transport configured with the ActiveEnterprise message wire format. It supports both UTF-8 and Latin-1 message encodings.

The message encoding property is set on the project itself at design-time, and when creating a TIBCO administration domain. The default for both is ISO8859-1.

• To change the message encoding on the project, select the root folder and, under the Project Settings tab, change the value for the TIBCO Message Encoding field. This affects only projects used with Adapter Tester, TIBCO BusinessWorks Tester and projects exported to local repositories.

• To change the message encoding for the administration domain, edit the repo.encoding property in the administration server's tibcoadmin<domain-name>.tra configuration file, which is located in <install-path>/tibco/administrator/5.1/bin. This affects all projects managed by the administration server.

1-1LIC31 Summary The adapter cannot convert a TIBCO message to an EJB message or vice versa, if the ActiveEnterprise schema defined for the adapter service contains the any data type, and if it has been populated by a complex or user-defined ActiveEnterprise schema class. However, the adapter can handle any data types correctly if they are populated with scalar data.

Workaround Attach the complex schema directly to the adapter service.

OR

If a TIBCO message can contain multiple types, create a Union with all the possible data types, wrap this union in a schema class, and attach this to the adapter service.


Known Issues | 23

1-5YGFL Summary The adapter is not compatible with the IBM WebSphere Test Environment available in IBM Visual Age (all versions).

Workaround None.

1-6QXYHS Summary The adapter displays an error when it is configured for an operation schema with a return type as sequence object.

Workaround Configure the OUT parameter for the operation and associate the sequence to this out parameter instead of specifying the sequence object as the return type for an operation.

1-7Q3I3 Summary The adapter does not allow the configuration of a reply subject with the publication service.

Workaround It is recommended that you use the request-response invocation service instead.

1-Y1M59 Summary If a request-response server service fails to initialize, it will be created using configuration information from the last successfully initialized request-response server service that had the same subject name and endpoint information.

Workaround Make sure that the request-response server services have unique configuration information. This will ensure that incorrectly configured services are not initialized.

Code Generator

1-5Y86G Summary The code generator does not allow the specification of multiple operations with the same name.

Workaround You must use unique operation names.

1-WJIE1 Summary For a class inheritance hierarchy in the repository, the adapter does not generate code for derived classes by starting at the base class. It only generates code for the base class.

Workaround To ensure that code is generated for all derived classes and the base class, begin by generating code for the last derived class in the inheritance hierarchy.

1-WJIEP Summary The code generator cannot generate code for multiple endpoints that are attached to the same operation class.

Workaround Specify one operation class for each endpoint.

Defect # Summary/Workaround


24 | Release Notes


tibco adapter™ for ejb - tibco product documentation · pdf file† jboss 3.2.3...

Documents