Index Changes
This is version 1. It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Release Notes for Sun GlassFish Enterprise Service Bus v2.1

What Is GlassFish ESB?

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 v2 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.

For screencasts and documentation for GlassFish ESB, refer to: http://wiki.open-esb.java.net/Wiki.jsp?page=GlassFishESBDocs

Compatible OS Platforms and External Systems

Note: The "System Virtualization Support in Sun Java System Products" statement applies to GlassFish ESB: http://docs.sun.com/source/820-4651/index.html

Design-Time

The OS platforms that are compatible with GlassFish ESB design-time components are the same as those that are compatible with NetBeans 6.1:
  • Sun Solaris 10 SPARC (64 bit)
  • Sun Solaris 10 x86 (64 bit)
  • Sun Solaris 9 SPARC (64 bit)
  • OpenSolaris 2008.05
  • Macintosh OS X 10.5 x86 (32 bit)
  • Macintosh OS X 10.5 PPC (32 bit)
  • Microsoft Windows XP SP2 and SP3 (32 bit)
  • Microsoft Windows 2003 R2 SP2 (32 bit)
  • Microsoft Windows Vista Business SP1 (32 bit)
  • Microsoft Windows 2000 SP4 (32 bit)
  • Red Hat Enterprise Linux AS 4 (64 bit)
  • Red Hat Enterprise Linux AS 4 (32 bit)

Runtime

The OS platforms that are compatible with GlassFish ESB runtime components are the same as those that are compatible with GlassFish v2 UR2:
  • Sun Solaris 10 SPARC (JVM: 32 bit and 64 bit)
  • Sun Solaris 9 SPARC (JVM: 32 bit)
  • Sun Solaris 10 x86 (OS: 32 bit and 64 bit; JVM: 32 bit)
  • OpenSolaris 2008.05 (evaluation support only)
  • Macintosh OS X 10.5 x86 (OS: 32 bit; JVM: 32 bit)
  • Macintosh OS X 10.5 PPC (OS: 32 bit; JVM: 64 bit)
  • Microsoft Windows XP SP2 and SP3 (OS: 32 bit; JVM: 32 bit)
  • Microsoft Windows 2003 R2 SP2 (OS: 32 bit; JVM: 32 bit)
  • Microsoft Windows Vista Business SP1 (OS: 32 bit; JVM: 32 bit)
  • Microsoft Windows 2000 SP4 (OS: 32 bit; JVM: 32 bit)
  • Red Hat Enterprise Linux AS 4 (OS: 64 bit; JVM: 32 bit)
  • Red Hat Enterprise Linux AS 4 (OS: 32 bit; JVM: 32 bit)
Note: Macintosh OS X is supported for development purposes only, and is not supported for production deployments.

External Systems

The following databases are compatible with the Database Binding Component:
  • Oracle 11g
  • MySQL 5.0
  • DB2 9.1
  • SQL Server 2005 with SP2
  • Sybase 15

The following databases are compatible with the Data Mashup Service Engine and the BPEL Service Engine:

  • Oracle 11g
  • MySQL 5.0

The following LDAP servers are compatible with the LDAP Binding Component:

  • Sun Java System Directory Server Enterprise Edition 6.3
  • Windows Server 2003 Active Directory
  • OpenLDAP 2.3.39
  • OpenDS 1.0

Components and Features

This initial release of GlassFish ESB consists of the following:
  • Service engines and project types/editors:
    Java EE, BPEL, XSLT, Data Mashup, Composite Application, CASA editor, WSDL editor
  • Binding components:
    HTTP, File, JMS (includes JMSJCA), Database, LDAP, FTP
  • Documentation:
    Wiki pages, guides, tutorials, and screencasts
  • The GlassFish ESB community

For a list of supported standards, refer to: https://open-esb.dev.java.net/glassfishesb/techdetails.html

Known Issues

Related to Open ESB:
  • Database Binding Component
  • LDAP Binding Component
  • FTP Binding Component
  • File Binding Component
  • JBI Management
Related to NetBeans:
  • BPEL
  • XSLT
  • Composite Application

Database Binding Component


431 (Database BC): The ojdbc5.jar driver for Oracle does not support prepared statements; attempting to do so yields the following error message:
  java.sql.SQLException: Unsupported feature

No resultset is populated, and java.lang.string is selected for every parameter, regardless of datatype.

To work around, use DataDirect drivers instead of ojdbc5.jar.

432 (Database BC): Although BLOBs (binary large objects) can be inserted, they are not selected and retrieved properly and no error message is displayed.

453 (Database BC): No error message displayed if too many parameters are supplied in an insert prepared statement. For example, "insert into table values(?,?,?,?,?)" into a 3-column table causes a runtime exception, and no parameters are added.

494 / 495 / 496 / 497 (Database BC): When any of the following are changed in the Prepared Statement Wizard, the changes are not reflected in the resulting XSD:

  • parameter name (column name)
  • data type
  • resultset parameter name
  • resultset data type

499 (Database BC): When a prepared statement is used to update or delete parameters, the result displays the default java.lang.String datatype irrespective of the actual datatype. This is because the DataDirect connect of JDBC driver for Oracle does not support returning parameter metadata information for an update statement with mixed literal and parameterized arguments.

To work around, manually change the datatype of the parameter in the generated XSD.

517 (Database BC): Built-in functions require an alias to avoid misinterpreting names of elements with special characters.

For example, the prepared statement "select avg(float) from table where number in(...);" yields the following error:

  ERROR: s4s-att-invalid-value: 
  Invalid attribute value for 'name' in element 'element'. 
    Recorded reason: cvc-datatype-valid.1.2.1: 
    'AVG(NUMBER)' is not a valid value for 'NCName'.

To work around, use an alias for the function. For example: "select avg(float) avg from table where number in(...);"

533 (Database BC): DataDirect driver does not return back correct metadata, resulting in incorrect resultset for output parameters of stored procedures.

This is a driver error; work ticket W809210001 has been filed with DataDirect about the metadata call getProcedureColumns() returning incorrect parameters.

771 (Database BC): The resultset from a MySQL stored procedure is not shown in the stored procedure wizard, even though runtime operation is correct.

866 (Database BC): Cannot insert datetime value in sqlserver 2005 using sqljdbc.jar driver.

This is a user error involving spaces and parentheses. See the resolution at: http://forums.microsoft.com/technet/ShowPost.aspx?siteid=17&postid=4061403

1087 (Database BC): Stored procedures do not support the BLOB (binary large object) datatype. Although the procedure runs without generating an error, a select statement fails to yield any BLOB data.

LDAP Binding Component

804 (LDAP BC): An "AuthenticationNotSupportedException" occurs when the authentication type is not agreed between server and client; for example, when a client specifies "strong" SSL authentication to handshake with a DSEE 6 server that handles "none", "simple", etc., but not "strong".

845 / 864 (LDAP BC): Normalized message properties functionality does not work; when the LDAP BC is used to search against an LDAP entry or perform any other LDAP operation, it incorrectly takes values from the WSDL instead of picking values defined in the BPEL.

905 (LDAP BC): When an application configuration file contains an underscore and an invalid credential is intentionally supplied, the test fails to run at all; it should instead throw an AuthenticationException.

924 (LDAP BC): No design-time validation is performed when an invalid root dn is supplied (such as "dc=sun" instead of "dc=sun,dc=com"), and the user is (incorrectly) allowed to create LDAP WSDLs. However, such a project (correctly) fails at runtime with a "No such object" error message.

1123 (LDAP BC): An error occurs upon rapidly inserting ~5000 records into LDAP, with error text such as the following:

  ...jbi.ldapbc.util.LdapConnection|[...]
    Cannot establish connection after 0times  check the external system for Connection

  ...jbi.ldapbc.util.LdapConnection|[...]
    javax.naming.CommunicationException: <host_ip>:1389 
    [Root exception is java.net.BindException: Address already in use: connect]


FTP Binding Component

796 (FTP BC): In ftp:transfer, setting messageCorrelate to "true" causes the FTP BC to expect the input file to match a fixed pattern (req.UUID) so that the UUID can be used as the ID to correlate a request with a response.

828 (FTP BC): Certain validations done by NetBeans when building a project are not done by command-line builds (ant tasks). For example, a project specifying a nonpositive or noninteger FTP BC poll value (pollIntervalMillis) can be built in ant but fails validation in NetBeans.

832 (FTP BC): On all operating systems, the delimiter for path components specified for preReceiveLocation (in sendTo, receiveFrom, and so forth) is the forward slash (/). Using the backslash instead results in errors such as the following:

  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.


File Binding Component

The File BC supports encodings in UTF-8 format only; if the encoding is in non-UTF-8 format, the File BC fails to read the input data. However, data of any encoding style (either UTF or non-UTF-8) and binary data can both be forwarded as attachments.

To work around the UTF-8 limitation:

  • To read non-UTF-8 data, employ a custom encoder upstream of the File BC and convert it to UTF-8 format, which in turn can be provided as input to File BC.
  • To write non-UTF-8 data, route the output from the File BC to a custom encoder and convert it from UTF-8 to the preferred encoding format.

For more information, refer to "Designing Custom Encoders".

JBI Management

411 (JBI Management): The application verifier behaves inconsistently when "startOnVerify" is true, depending on the state of the component. If "startOnVerify" is true, the verify command should always start a stopped or shutdown component before performing verification, and then return the component to its original state. Instead, the verify command fails on first iteration (and starts the component); then it succeeds on the second iteration.

To work around, do one of the following:

  • Start the required components before running the first verify command.
  • Re-run the verify command after the initial failure.

512 (JBI Management): If a credential such as a keystore or truststore password is empty, it nonetheless appears pre-populated with data because it displays as "******".

No workaround is required; If a password is actually null, the obfuscated string is ignored.

884 / 885 (JBI Management): Components should be configurable when in the stopped state. Currently, neither runtime nor the admin console allow a component to be configured unless it is in the started state.

To work around: Start the component before attempting to configure it.

Open JBI Component issue 559 (JBI Management): When a component (such as the BPEL SE) is shut down while there are certain kinds of typographical errors in its configuration settings, it cannot be restarted and its configuration settings cannot be edited within the NetBeans IDE or the web console.

To work around: The typographical errors must first be corrected by manually editing the GlassFish configuration files, thus allowing the component to be restarted.

BPEL

Note: For BPEL SE stop/restart issues, see JBI Management, above.

153564 (BPEL editor): When Logging is enabled for a BPEL activity, and the activity (or its parent/grandparent) is then called with the "Wrap with" action or moved with the mouse, the activity (or its parent/grandparent) disappears and a NullPointerException is thrown.

To work around: Undo the action, disable logging, and then redo the action.

148288 (BPEL project): If a BPEL project is deleted (using the "Delete Source" option) and a new project is then created that reuses the same name, then the newly created project's Properties cannot be opened.

To work around: Stop and then restart the NetBeans IDE.

XSLT

153469 (XSLT project): When a WSDL is referenced by an XSLT project, its location is saved as a relative path within the project, and the project fails to deploy properly.

To work around, import the WSDL rather than referencing it.

Composite Application

148024 (Composite Application project): Cannot create a testcase using the soap12 binding, even though GlassFish otherwise supports SOAP 1.2.

To work around: Use a soap binding (instead of soap12).

152455 (CASA editor): When the design canvas of the CASA editor is at certain sizes, the display of its scrollbars oscillates and CPU usage goes to 100%.

To work around, increase the size of the window or of the CASA editor design canvas so that scrollbars do not display.

152449 (Composite Application project): When a new project type is freshly installed, the Composite Application project is initially unable to determine the service engine type and is thus unable to deploy the service unit. The following error message is displayed:

  Cannot add JBI module <project_type>. 
  Its target component type <engine_name> is unknown.

To work around: Stop and then restart the NetBeans IDE.

153537 (Composite Application project): Cannot rebuild a Composite Application project after a Service Unit (SU) has been deleted from it.

To work around: Manually edit the build-impl.xml file and delete all sections that operate on the deleted SU.


Return to GlassFish ESB Documentation Home

JSPWiki v2.4.100
[RSS]
« Home Index Changes Prefs
This particular version was published on 18-May-09 11:27 AM, -0700 by CarolT