Not logged in | Login
GFESB Release Notesv 2.1
GlassFish ESB delivers a lightweight and agile ESB platform that packages the innovation happening with Project OpenESB into a commercially supported, enterprise-class platform. GlassFish ESB builds on over 18 years of Sun expertise within SOA, ESB, integration, and server-side Java platforms. In essence, GlassFish ESB is a binary distribution that combines technology from Project OpenESB, the GlassFish application server, and the NetBeans IDE communities into a supported, commercial distribution. GlassFish ESB is compatible with a number of JBI-compliant plug-ins that provide a range of different technical capabilities.
This topic provides information about changes made to GlassFish ESB between versions 2 and 2.1. If you have any questions, go to the GlassFish ESB web site at http://open-esb.dev.java.net.
To access all the GlassFish ESB documentation in HTML format, go to the GlassFish ESB documentation page at http://wiki.open-esb.java.net/Wiki.jsp?page=GlassFishESBDocs.
GlassFish ESB includes the following new features and components in version 2.1:
GlassFish ESB includes the components listed below.
GlassFish ESB is divided into design-time components, which run on the NetBeans IDE, and runtime components, which run on the GlassFish application server. Design-time and runtime components each support a specific set of operating systems. In addition, several GlassFish components support external systems, such as database platforms, LDAP servers, JMS servers, and so on.
For a complete list of supported operating systems and external systems, see GlassFish ESB Supported Operating Systems and External Systems.
The following are known issues for the BPEL Service Engine:
The following are known issues for the Data Mashup Service Engine:
The following are known issues for the File Binding Component:
The following are known issues for the FTP Binding Component:
FTPBC-E004026. Exception when preparing ftp connection parameters in inbound processor. java.lang.Exception: FTPBC-E004019. No directory name found in PreReceiveLocation [...] when PreReceiveCommand is RENAME or COPY.
The following are known issues for the IEP Service Engine:
The following is a known issue for the Java Application projects with JAXB:
The following are known issues for the LDAP Binding Component:
The following are known issues for the XSLT Service Engine:
The following is a known issue for configuring GlassFish ESB cluster instances:
asadmin update-jbi-application-variable --component=sun-jms-binding name=value
The following are know issues for Composite Application (CA) projects:
Cannot add JBI module ''project_type''. Its target component type ''engine_name'' is unknown.
To work around this issue, stop and then restart the NetBeans IDE.
The following are known issues for installation and upgrades:
The following are known issues in managing JBI components:
The following is a known localization issue:
To work around this issue, use the GlassFish Admin Console to retrieve the JNDI value to enter for the Connection URL. The value is located under Resources > Connectors > Admin Object Resources.
The following is a known database issue:
|65||22-Sep-09 12:22 PM, -0700||CarolT||33109||to previous|
|64||30-Jun-09 13:16 PM, -0700||CarolT||32705||to previous | to last|
|63||17-Jun-09 14:12 PM, -0700||CarolT||32515||to previous | to last|
|62||17-Jun-09 14:12 PM, -0700||CarolT||32515||to previous | to last|
|61||16-Jun-09 17:21 PM, -0700||MarkWhite||32184||to previous | to last|
|60||16-Jun-09 12:38 PM, -0700||FrankKieviet||32170||to previous | to last|