|
|
|
| Sun Java Business Integration (JBI) | |
Java™ Business Integration
Software Developer Kit 1.0.1
Release Notes
Java™ Business Integration (JBI) Reference Implementation 1.0.1 is an implementation of the 1.0.1 level of the Java™ Business Integration Specification (JSR-208) as of June 1, 2005.
These Release Notes contain important information available at the time of release of JBI Reference Implementation 1.0.1. Requirements, known issues and limitations, and other information are addressed here. Read this document before you begin installing and using JBI Reference Implementation.
This document contains the following sections:
About Java Business Integration Reference Implementation
The Java™ Business Integration Reference Implementation is an implementation of the 1.0.1 level of the Java™ Business Integration specification (JSR-208) as of June 1, 2005. This implementation is designed to run on Sun Java System Application Server Platform Edition 8.1 2005Q2 UR2. It provides a working implementation of JBI technology and and demonstrates how it can be used to integrate applications in a SOA environment.
This section includes:
What's Included
- JSR-208 Reference Implementation as of the 1.0.1 version of the JBI Specification (June 1, 2005)
- CLI-based installer that can also run in silent mode
- File-based Binding Component
- SOAP Binding Component
- Sequencing Service Engine
- XSLT-based Transformation Service Engine
- Demo application with an ant script for installing and running the demo
- Java source code for the Reference Implementation and all sample components
- Javadoc for the public APIs and SPIs defined by JSR-208
- Javadoc for the implementation classes
Hardware and Software Requirements
This section lists the requirements that must be met before installing the JBI Reference Implementation.
Platform Requirements
The following table lists the operating systems that are supported for Java™ Business Integration Reference Implementation.
On UNIX®, you can check your operating system version using the uname command. Disk space can be checked using the df command.
Application Server Requirements
Java Business Integration SDK 1.0.1 version works with the current version of Sun Java System Application Server Platform Edition 8.1 2005Q2 UR2. (Before installing JBI SDK 1.0.1 you must install the Sun Java System Application Server.) To download this version please visit:
Known Issues and Limitations
This section describes known problems and associated workarounds for the JBI Reference Implementation. If a summary statement does not specify a particular platform, the problem applies to all platforms.
Bug ID
Summary
n/a
The JBI Specification states that Service Unit archives must contain a single JBI-defined descriptor file (Section 6.3.4 "Service Unit Packaging"). Currently, for backward compatibility, the sample components provided in the JBI Reference Implementation do not require descriptor files (jbi.xml) to be present inside Service Units deployed to those components. If a Service Unit does contain a descriptor file, the components do support it. In the future, the sample components will be updated to require the presence of a descriptor file in each Service Unit deployed to them. It is therefore recommended that all Service Units be packaged with a proper spec-compliant descriptor file.
6264085 Cancelling installation does not stop or roll back the installation.
If the installer "Cancel" button is clicked, the installer fails to stop and does not roll back the installation.
Solution
Allow the installation to complete, then use the uninstall option to remove the installation.
6265180 Service Assembly undeploy succeeds when error removing SA root path.
When a Service Assembly is undeployed, in certain cases the SA directory is not deleted due to file locking. If this happens, redeployment of the same Service Assembly fails with an exception "Duplicate service assembly".
Solution
In this scenario, stop the application server and delete the SA directory manually. Redeploy the service assembly after restarting the application server.
6265233
Transformation Engine doesn't close SU files when the SU is stopped or shut down.
The Transformation Engine is keeping some SU files open even after the SU is stopped or shut down. This causes problems undeploying the SU.
Solution
Shut down the Transformation Engine and manually delete the SU root directory.
6268637
Sequencing Engine transaction involving more than one service in servicelist fails.
With a servicelist in the Sequencing Engine that has two services, when a binding starts an XA transaction and sends a message to the Sequencing Engine's servicelist, the request goes to the first service but when it goes from the first service back to the Sequencing Engine it throws an exception and the service fails.
Solution
None available.
6274920
JDK log manager holds strong reference to java.util.logging.Logger instances
When a component requests a logger from JBI using the ComponentContext.getLogger() method, JBI uses the standard JDK logging facilities to create this logger. The JDK log manager never releases a Logger instance for the life of the JVM. There is a case where this causes a problem during a component upgrade. If a component provides a Resource Bundle for use by the logger, and that component is uninstalled and reinstalled without a JBI restart, the logger is still using the original Resource Bundle instead of the new one. Furthermore, if the name of the Resource Bundle changes betweeen the two version of the component, calls to ComponentContext.getLogger() will throw a javax.jbi.JBIException with this message: JBIFW1352: A logger with name {0} cannot be created using resource bundle {1}. A logger with the same name already exists using resource bundle {2}.
This bug is not in the JBI RI itself, but in the JDK.
Solution
The only solution when this situation arises is to restart JBI by restarting the appserver.
How to Provide FeedbackIf you have comments on the JBI Reference Implementation, you can send them to: jsr208-ri-feedback@sun.com
Copyright © 2004-2005 Sun Microsystems, Inc. All rights reserved.
Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at http://www.sun.com/patents and one or more additional patents or pending patent applications in the U.S. and in other countries.
SUN PROPRIETARY/CONFIDENTIAL.
U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements.
Use is subject to license terms.
This distribution may include materials developed by third parties.
Portions may be derived from Berkeley BSD systems, licensed from U. of CA.
Sun, Sun Microsystems, the Sun logo, Java and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the U.S. and other countries.
Copyright © 2004-2005 Sun Microsystems, Inc. Tous droits réservés.
Sun Microsystems, Inc. détient les droits de propriété intellectuels relatifs à la technologie incorporée dans le produit qui est décrit dans ce document. En particulier, et ce sans limitation, ces droits de propriété intellectuelle peuvent inclure un ou plusieurs des brevets américains listés à l'adresse http://www.sun.com/patents et un ou des brevets supplémentaires ou des applications de brevet en attente aux Etats - Unis et dans les autres pays.
Propriété de SUN/CONFIDENTIEL.
L'utilisation est soumise aux termes du contrat de licence.
Cette distribution peut comprendre des composants développés par des tierces parties.
Des parties de ce produit pourront être dérivées des systèmes Berkeley BSD licenciés par l'Université de Californie.
Sun, Sun Microsystems, le logo Sun, Java et Solaris sont des marques de fabrique ou des marques déposées de Sun Microsystems, Inc. aux Etats-Unis et dans d'autres pays.
Toutes les marques SPARC sont utilisées sous licence et sont des marques de fabrique ou des marques déposées de SPARC International, Inc. aux Etats-Unis et dans d'autres pays.