Importing and exporting EIS services Release Notes

© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Release notes

1.0 Description
2.0 Limitations
3.0 Known problems and workarounds
   3.1 Importing a C struct with an anonymous struct declaration
   3.2 Deploying applications with asynchronous reliability and interaction style properties

1.0 Description

This release notes file contains late-breaking information about limitations and known problems and workarounds for the following WebSphereR Integration Developer enterprise discovery wizards:

2.0 Limitations

None

3.0 Known problems and workarounds

3.1 Importing a C struct with an anonymous struct declaration

The C importer does not correctly handle anonymous struct declarations. For an example, see the following code:

typedef struct {
       char loanId[20];
       double loanAmount;
       char date[20];
       struct {
           char taxPayerId[10];
           char firstname[20];
           char lastname[20];
           char email[50];
       } Customer[1];
} LoanInfo;

The previous code does not import correctly. A workaround is to modifiy the declaration to put the anonymous struct declaration outside as a named struct. The following declaration is equivalent and will import correctly:

typedef struct {
         char taxPayerId[10];
         char firstname[20];
           char lastname[20];
           char email[50];
       } Taxpayer;

typedef struct {
       char loanId[20];
       double loanAmount;
       char date[20];
       Taxpayer Customer[1];
} LoanInfo;

3.2 Deploying applications with asynchronous reliability and interaction style properties

Asynchronous reliability and interaction style properties were added to the JMS and EIS export bindings to provide you with more options when using these bindings with your exports. 

 

To deploy an application that uses these properties to WebSphere Process Server, version 6.0.1 or earlier, you will need to add an interim fix to the server. Specifically, you will need to add APAR JR23428 - TOLERATION OF ENHANCED ARTIFACTS IN WPS/WESB FIX PACK 1, which is available on the WebSphere Process Server Support Web site.