© Copyright International Business Machines Corporation 2004, 2005. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This file is available in the following national languages:
| Brazilian Portuguese | Chinese - Simplified | Chinese - Traditional |
| French | German | Italian |
| Japanese | Korean | Spanish |
To view the latest version of this file, see the release notes at www3.software.ibm.com/ibmdl/pub/software/rationalsdp/rsa/60/html/readme_6011.html.
IBM® Rational® Software Architect 6.0.1.1 provides new functionality in the following categories and components:
Performance improvements
- Model query performance is improved, providing as much as a 50% faster model query returns.
- The memory management for the architectural discovery feature is significantly improved, providing increased performance when you work with complex model files.
- The memory management for the diagram editor is improved, providing increased performance when you work with model files.
- In previous versions of the product, when you used complex model files, adding attributes or ports to a diagram element might take an extended period of time. The time required to complete these tasks for complex model files is significantly reduced.
- In previous versions of the product, when you used complex model files, adding, renaming, or removing a package might take an extended period of time. The time required to complete these tasks for complex model files is significantly reduced.
- In previous versions of the product, a generic Eclipse resource change listener was used to receive all types of resource change events. A new listener has been implemented to only listen to post-change resource events. As a result, the product no longer attempts to process build notices and pre-change events, and provides increased performance in various standard development and team development scenarios.
- In previous versions of the product, when you worked with large numbers of elements in class diagrams, the pop-up menu might take an extended period of time to display. The time required to complete this task for complex model files is significantly reduced.
- In previous versions of the product, when you worked with complex model files, scrolling through a large diagram using the Outline view might result in a slow response from the product and a CPU utilization of 100%. The time required to complete this task for complex model files is significantly reduced.
EGL Builder performance improvements
The performance of the EGL Builder has been drastically improved. You can expect to see significant improvements in the amount of time required to build an entire workspace and in the amount of time required to build individual parts as they are being developed. In the past if you normally had the "Build automatically" preference turned off, try working with it turned on.
The first time each project is built using version 6.0.1.1 of EGL, the .project file, which is located in the root directory of the project, will automatically be modified so that it references the new EGL Builder. After this update has been completed, all future builds of the project will use the new EGL Builder. It is recommended that users manually invoke a build after starting V6.0.1.1 and loading the workspace, so that the projects will have been built with the new EGL Builder before future development takes place. A manual build can be invoked by selecting Project >Build All from the toolbar.
Note: If the option to Build Automatically is enabled, a project will be changed to use the new EGL Builder the first time version 6.0.1.1 of the product is started for an existing workspace or after a project is imported in both new and existing workspaces. If the option to Build Automatically is disabled, it is necessary to invoke a build manually to migrate to the new EGL Builder. All new projects created with version 6.0.1.1 of the product will already be configured to use the new EGL Builder.
New EGL Problem Types
As part of the builder performance improvements, new problem types have been created for EGL. These problem types are used when displaying errors in the Problems view. After installing V6.0.1.1, it may be necessary to update the Problems View so that these new problem types are displayed correctly. To update the view, select the Filters option from the Problems View drop down menu. In the dialog that is displayed, make sure that the following types have been selected (you will need to scroll the table to find the EDT entries):
- EDT Context Specific Problem
- EDT File Problem
- EDT Problem
- EDT Syntax Problem
Message Differences
As part of the builder performance improvements, an effort was made to be more consistent with regards to the validation error messages that are issued. While all of the same error conditions are caught, it is possible you may see a different number of error messages than before. Also, the text of the messages issued may not be the same as before. Previously, when validating referenced functions from a part (program, library, etc) which invoked the function, all error messages were placed on the function invocation statement. These error messages are now placed in the invoked function on the specific line where the error occurred. Each error message contains the name of the invoking part. This makes it much easier to find the reason for the error.
Use Form Syntax Change
As part of the builder performance improvements, we have made changes in how we process forms. However, this may cause ambiguity errors in the case where a form group has like-named fields on multiple forms and a program has unqualified references to those fields.We have added a new "Use forms" syntax so the customer can specify which forms to look at during name resolution.
use <formgroup-name>.<form-name>, <formgroup-name.form-name>, etc.If you have new validation errors related to resolving form fields, to fix the problems you can either fully qualify your references to the form fields or you can use a new action called "Organize Used Forms". This action analyzes the program to see what forms are actually used and then creates the appropriate Use statement. This action is available on the context menu for an EGL project, EGL package, and EGL file. It is also available from the context menu of the EGL Editor. If there are serious errors with the program, such as a syntax error, unresolved use statements, or using multiple non-help form groups, this action puts up a message saying that it can not run due to errors in the program, and no changes will be applied. However, this action does work when there are other errors, such as the ambiguity error that this action is meant to fix. If there are serious enough errors where EGL does not recognize an I/O statement, this action can not detect the form on that statement and the results may not include all the forms used. Thus, other than the ambiguity error, it is recommended that this action is run with a cleanly compiled program.
Note: useformGroup is still supported and can be used. It is a short cut for listing every form in the form group on the use statement.
EGL SQL Retrieve option for COBOL compatibility
At EGL declaration time, you can use the SQL retrieve feature to create an SQL record from the columns of an SQL table. If you want new SQL records to be compatible with COBOL programs (that is, to have fixed records with level numbers for structure items, and to use CHAR instead of STRING primitive types), select the Create COBOL compatible record definition check box on the SQL Retrieve Preferences window.
JSF Table's Row Edit button label can be customized
Three new Row Edit attributes added to allow button label customization, editLabel for the Edit button label, saveLabel for the Save button label and cancelLabel for the Cancel button label.
OCL improvements in UML modeling
- You can now add OCL pre-conditions, post-conditions, and body conditions to operations.
- You can now parse operation constraints. Also, you can now take advantage of the content assist functionality when you work with operation constraints.
- In this version of the product, when you validate an OCL constraint, the validation checks operation constraints.
- This version of the product includes support for the OCL parser finding enumeration literals and nested classifiers.
- This version of the product includes rename re-factoring support for the following model elements:
Note: Re-factoring support only applies to the models that are open in your workspace.
- Classifiers
- Enumeration literals
- Operations
- Packages (as they pertain to qualified names)
- Parameters
- Properties
Team environment
- You can now ensure that all model element UUID values are unique.
- You can now assign a new UUID to an unreferenced model element.
UML transformations
- Now, when you perform a UML-to-Java transformation by using the Replace UML elements option, the transformation preserves the validity of the source UML models according to the UML Superstructure Specification, v2.0, dated July 4, 2005. This is done by replacing the transformed classes, interfaces, and enumerations with shortcuts to their Java equivalents. The transformation moves the contents of the elements that it does not transform to their nearest package, or if this is not possible, it deletes them. The deleted contents include the untransformed structural elements that cannot be owned by packages, such as connectors and ports, and all untransformed behavioral elements, such as interaction, state machine, and activity-related elements.
- You can now perform a UML-to-C++ transformation using the Replace UML elements option.
This fix pack includes Rational Software Architect 6.0.1 and the following interim fixes:
- (PK10974, PK10976) An error occurs when you compare and merge three model file versions by using Compare with each other option.
- (PK14275) An index-out-of-bounds error occurs when you compare and merge model files.
- (PK15320) Error occurs after merge of models.
- (PK11004) The compare and merge operations might not function properly after you perform a cut-and-paste refactoring to duplicate model content.
There is now support for using the DB2® Universal JDBC Driver |for building Java™ stored procedures which have source larger than 32K |and target a DB2 UDB for z/OS® V7 server. Before this support was added, the Universal Driver was supported only for DB2 UDB z/OS V8 Java stored procedures. In order for this support to work, you must install DB2 for z/OS V7 APAR (PK01445).
(PK12617) When stopping at a breakpoint the debugger performs an inefficient search for the Java source.
- (PK12468) A NullPointerException is thrown when a union is used in the select statement.
- (PK13735) A clob item object of size greater than 8k when written to a file resource does not contain all the data in the clob item.
- (PK15122) When using an SCM system, an eglbld file cannot be modified after check out.
- (PK11964) EGLCMD gives an error complaining about the command file not being found
- (PK14282) Some runtime messages use the language specified using the vgj.nls.code runtime property. Other runtime messages were in the language of the default locale regardless of how the vgj.nls.code was set.
- (PK14107) The Value of a target item remains unchanged on an assignment operation which causes a user overflow error.
- (PK13732) The System function: loblib.attachClobToFile does not produce the expected behavior according to the documentation.
- (PK13842) Cannot dynamically set the destHost and destPort values similar to how you set the userid and password values in the EGL generation wizard and the EGLCMD/EGLSDK commands.
- (PK13149) Setting the MODIFIED attribute of an AUTOSKIP field does not remove the AUTOSKIP.
- (PK13303) Cannot return German date format after applying appropriate properties and date mask values within an eglbld file.
- (PK14663) Add import statements for all tables; add use declarations for message tables used in statements.
- (PK10269) Need to handle subapplications for Smalltalk.
- (PK14662) Negative sign displaying because form field has no sign property defined.
- (PK12102) An error occurs when you print a diagram or preview a print operation for a diagram that is from a previously created workspace.
- (PK14841) An error occurs during validation.
- (PK02927) An error occurs in an OCL expression if a named classifier or feature in the user model contains any characters beyond the basic ASCII character set.
- (PK03169) An error occurs when you process multi-line OCL expressions.
- (PK07166) An error occurs when you attempt to use the oclAsType() operation to construct valid OCL expressions.
- (PK07772) An error occurs when you attempt to evaluate the allInstances() OCL operation on a UML metaclass. The evaluation does not return a result.
- (PK09674) The basic view types, such as Note and Text, are only exposed by an internal interface.
- (PK11514) The architectural discovery feature does not efficiently use the computer’s memory when it runs the Singleton and Inheritance pattern rules.
- (PK13418) Methods are missing from the IImportDataModel interface.
- (PK09523) The Deploy option is greyed out for EJB projects when viewed from the Java perspective.
- (PK09536) If a module contained in an EAR does not have an entry in the module maps file, it throws a null pointer exception when trying to add a new module.
- (PK04446) For a Web project that references a Java project as a Web library project, when creating the WAR file (either by exporting the EAR or by exporting the WAR directly), the created WAR file contains extra metadata files that should be omitted.
- (PK10262) Running a Web application on the server without building the workspace results in missing classes.
- (JR22375) WAR files are not imported properly.
- (PK10262) Web library classes fail to load on a WebSphere® Application Server 5.x.
- (PK09191) There is a null pointer error using EJBs with JSF.
- (PK14576) The Web service resource is generated outside of Eclipse and the synchronization fails.
- (PK13756) A headless Ant build generates exceptions.
- (PK10740) The life cycle listener wizard fails to load if either no dynamic Web projects exist in the workspace, or something other than a dynamic Web project was selected prior to opening the wizard.
- (PK10767) If an EJB project has two source folders, only the first source folder that was found is recognized in the ejb-jar.xml file.
- (PK08976) Invalid handle after modifying the context root for a J2EE 1.2 project.
- (PK12579, PK12623) EJB relationship editor incorrectly shows the foreign keys on the wrong side.
- (PK12738) The classpath of an imported EJB project is not set correctly.
- (PK12364) Adding an EJB reference results in a duplicate entry being added in the classpath.
- (PK11260) The EAR deployment descriptor can get out of synch if you modify the xml files outside of the workspace editors.
- (PK12340) Attributes are not being read from the session variables. They can only be read from the properties file.
- (PK11618) Radio button groups cannot refresh correctly.
- (PK09168) Synchronization between JSP files and the Properties view does not update the property values correctly.
- (PK06790) Mailto links cannot be used in a JSF portlet.
- (PK12852) Tabbed panels require that forms be located within the tab.
- (PK13145) When client-side validation is enabled for an JSF inputText field of type date/time and the format of the field did not include "dd" (day of month), an input value fails validation.
- (PK13702) When a file is being uploaded with fileupload, no more Faces requests can complete their cycle until file upload completes.
- (PK09669) If you try to change dynamically the read-only property of an inputRichText, the value will always appear in read-only mode at run time.
- (PK13876) Enabling client side caching disables decode method .
- (PK09580) Some Javascript functions do not work with the <h:inputrichtext> custom tag.
- (PK09629) A warning occurs when dropping a <h:inputrichtext> onto a JSP file.
- (PQ99999, PK11184) Even when h:commandLink components are rendered="false", the separator bars are still rendered.
- (PK12914) Cannot assign default values to fields in a new row when it is added to the datagrid.
- (PK12362) There is a problem with enctype in JSF pages.
- (PK09633 ) The <r:inputrichtext> tag produces incorrect output.
- (PK07608) Fields with MaskConverter cause a conversion error if the field is left empty.
- (PK07517) Browser error 500 occurs if the rows attribute is not set on a datatable when a gotopager is used.
- (PK14376) There is a problem with a JSF multi-part form and DBCS characters on Solaris.
- A table caption can now be added using a 'caption' facet containing an outputText component, for example:
<h:dataTable id="table1" value="#{tabledat}" var="vartabledat">
<f:facet name="caption">
<h:outputText value="text" styleClass="className" />
</f:facet>
.......rest of table.....
</h:dataTable>- Scope, axis and dir attributes can now be rendered using the f:attribute tag within the h:column component. Scope and axis attributes will just be applied to cells within then body of the table. Dir attribute will be applied to body, header and footer cells of the rendered column usage , for example:
<h:column id="column1">
<f:attribute value="row" name="scope" />
<f:attribute value="Price" name="axis" />
<f:attribute value="ltr" name="dir" />
columnn contents.....
</h:column>
(PK13332) When you publish a diagram that contains two class instances that are connected by a link instance, the model might not publish properly.
- (JR22105) JSF page template cannot be displayed in the Preview page.
- (JR22052) Adding a non-breaking space into a JSP file causes a JSP:translate error.
- (PK13434) When entering text into a JSP file, the text is entered backwards.
- (PK03176) The *+xml mime type is not interpreted as XML content in a JSP file.
- (PK13014) An included JSPF fragment is underlined as an error with misleading hover text.
- (PK13447) When the product is started, all portal and portlet projects are unnecessarily rebuilt.
- (PK11791) Cannot use the import wizard to import a portal application from a Websphere Portal Server v5.1 and run the
imported portal application on the portal test environment.
- (PK12573) A broken link appears for Struts tags containing dynamic expressions.
- (PK11225) An incorrect method is used to setthe value in the Validate field drop-down list
- (PK13382) A StringIndexOutOfBound exception occures during a build of a Struts-enabled Web project.
- (PK12117) There is an unrealized Struts action in a Web diagram.
- (JR21675) When creating a dynamic Web project with Struts enabled, the <bean:message /> tag in a JSP file does not work when the project is checked into Rational ClearCase® LT.
- (PK12387) A Struts config build using Rational ClearCase does not end.
- (PK02588) An error occurs when you drag a reflexive association class onto a diagram, in which two copies of the class are displayed.
- (PK09305) Performance degradation might occur when you scroll through a large diagram. In some scenarios, the CPU utilization is 100%.
- (PK10670) Association classes are not properly instantiated.
- (PK10846) You cannot allow items in an activity diagram to display icons when you use the Stereotype Shape Image mode.
- (PK11448) When you open a diagram, the following error might be displayed and the diagram does not open: "Unable to create part"
- (PK12931) If you create a class that implements an interface, that class inherits all the interface methods. If you then create a subclass of that class, the interface methods are no longer available.
- (PK12973) When you change the type of the data store to a signal, the element on the diagram has two slashes on each side.
- (PK13849) Associations from the AsociationClass class are not selected when you click Ctrl+A.
- (PK13991) When you add a UML association between two Java classes, model corruption might occur.
- (PK15533) When using a large project (60 MB), modeling actions like adding an attribute or adding a port takes a very long time (40 seconds).
- (PK11332) When referencing a remote server for XSL files, the validator is not using the correct base location.
- (PK13522) When an XML schemas has circular includes, attempting to map one schema to another causes a StackOverflow message.
- (PK12796) When validating XML documents that make use of the SOAP encoding schema, these documents may be marked as not valid.
For information about installing IBM Rational Software Architect Fix Pack 6.0.1.1, installation prerequisites, installing from a command line, and setting up a local mirror of the update server, see the installation instructions at http://www3.software.ibm.com/ibmdl/pub/software/rationalsdp/rsa/60/install_instruction/6011/install.html.
No additional hardware requirements are necessary to install this fix pack.
You can install this fix pack for use with IBM Rational Software Architect 6.0, 6.0.0.1, or 6.0.1. Before you install the fix pack, you must install IBM Rational Product Updater 6.0.1.
Note that in addition to the operating systems listed in the Version 6.0 Installation Guide, the following operating systems are supported if you install this fix pack:
- Windows® Server 2003 Standard Edition with Service Pack 1
- Windows Server 2003 Standard Edition with Service Pack 1
If you use local updates and have more than one product installed, you must download the 6.0.1.1 fix packs for all installed products to your local update site. This is because there are dependencies among them. If you have multiple products installed and download only one fix pack and run the Rational Product Updater, the Updater will give you a warning when you search for updates that one of the required updates is missing. Again, this situation only applies to customers who use local update sites.
To simultaneously install the fix packs, download them to your local update site. Then install all fix packs at the same time from the update site by using the Rational Product Updater.
The version 6.0.1 documentation failed to include the following limitations and recommendations for the EGLSDK and EGLCMD commands.
For both:
- To work around an OutOfMemoryError when running either EGLSDK or EGLCMD, try increasing the JVM heap size. Use the following command:
java [-msstart_sizem] -mxmax_sizem application
start_size
An optional beginning size, in megabytes, for the JVM heap used in running application.
max_size
The maximum JVM heap size, in megabytes, to be used in running application. This should not be greater than half the RAM available to the system.
application
Either EGLSDK or EGLCMD, followed by its usual parameters.
The following example assumes the system has 2GB RAM available:
java -ms512m -mx1024m EGLCMD EGLListDetailForTUI/EGLCommandFile.xml -data D:\WorkSpaceFor EGLSDK:
- Make sure that emfworkbenchedit.jar is in your Java classpath. The jar file is in the following directory:
installationDir\rwd\eclipse\plugins\com.ibm.wtp.emf.workbench.edit_version\emfworkbenchedit.jarinstallationDir
The product installation directory, such as C:\Program Files\IBM\RSPD\6.0. If you installed and kept a Rational Developer product before installing the product that you are using now, you may need to specify the directory that was used in the earlier install.
version
The installed version of the plugin; for example, 1.0.0- If you wish to enable COBOL generation for either z/OS® or iSeries™, make sure that the runtime jar file eglgencobol.jar is in your class path. The jar file is in the following directory:
installationDir\egl\eclipse\plugins\com.ibm.etools.egl.batchgeneration_versioninstallationDir
The product installation directory, such as C:\Program Files\IBM\RSPD\6.0. If you installed and kept a Rational Developer product before installing the product that you are using now, you may need to specify the directory that was used in the earlier install.
version
The installed version of the plugin; for example, 6.0.0- EGL does not support the generation of pageHandlers from the SDK. To create pageHandlers in batch mode, use EGLCMD.
For EGLCMD:
- Close all instances of the workbench UI before executing EGLCMD from a command prompt.
- If you use the wizard to create the command file, do not move that command file to another directory. The command file must be in the workspace containing the parts EGL is using to generate code.
- Use the -data option to specify the workspace for EGLCMD. Otherwise EGL will use the default workspace, which may not be the one you want.
- When you generate a pageHandler with EGLCMD, be sure to use the build descriptor option genProject. This allows EGL to handle all the J2EE deployment information automatically.
- If you use EGLCMD and the genDirectory build descriptor option for a project that contains no Web components, EGL will compile the programs outside the workbench. For this reason the Java compiler (javac.exe) must be in the system path and the EGL Java generation code (eglbatchgen.jar, in the bin directory of your installation directory) must be in the system classpath.
- If you are generating for iSeries, you may also need to put xml.jar on your classpath (you will find it in eclipse\jre\lib in you installation directory). Because having too many items in the classpath for EGLCMD can also cause problems, you should have only these four files in your classpath to generate for the iSeries: eglutil.jar, startup.jar, eglbatchgen.jar, and xml.jar.
Starting with version 6.0.1.1, you can create arrays of any type of record, as long as you are generating Java. If you generate COBOL, the old rule still applies: you can only make an array of Basic, SQL, or DLISegment records.
The following functions were documented incorrectly:
These "attach" functions associate a variable (either BLOB or CLOB) with a file resource (either specified or temporary system file), but do not write the contents of the variable to that resourse. Any prior memory or file associations are released. Subsequent operations, such as reading from a database into the variable, will update the file.
- attachBlobToFile()
- attachBlobToTempFile()
- attachClobToFile()
- attachClobToTempFile()
Previously, when you included a limited-length string variable in an EGL string concatenation and itemsNullable was YES, the variable's value was padded with blanks to its maximum length. When itemsNullable was NO, no padding was added. Starting with version 6.0.1.1, no padding will ever be added.
There is no support for making JDBC connections from Crystal Reports to z/OS and iSeries-based database products.
The Crystal Reports XML driver requires an application server to be at least J2EE 1.4 compliant, and therefore does not support Websphere Application Server v5.x runtime, which is J2EE 1.3 compliant.
In Informix 4GL, the function GET_FLDBUF( ) returns the character values of the contents of one or more fields in the currently active screen form. The function accepts values of fieldNames, screen record field names, screen array field names, and database table field names.
There is an undocumented feature in Informix 4GL whereby if you pass to the GET_FLDBUF() function a nonexistent screen-record, screen-array, or table-reference, the 4GL runtime it will ignore it and resolve it to first instance of fieldName in the current active form.
For example, a function call like this GET_FLDBUF(nonExistentReference.fieldName) where "nonExistentReference" cannot be resolved to any screen-record, screen-array, or table-reference, the 4GL runtime will resolve it as if the function was just passed "fieldName", like this GET_FLDBUF(fieldName).This behavior is not supported in the 6.0.1.1 RAD/RWD release of EGL nor in the Conversion Tool.
VisualAge® Generator applications understand 24 function keys (PF1 to PF24) as well as 3 action keys (PA1 to PA3). The way the user sends some of those keys in EGL has changed.
For Function Keys PF1 to PF12 -
The functionality continues to work the same way as in previous releases.
For Function Keys PF13 to PF24 -
In VisualAge, this was accomplished by pressing Alt and PF1 to PF12.
In EGL's GUI runtime, this is accomplished by pressing Shift + PF1 to PF12. NOTE: This method does not work for the EGL Curses runtime.
In EGL's GUI or Curses runtime, this can also be accomplished by pressing Ctrl-S, then PF1 to PF12.
For Function Keys PA1 to PA3 -
In VisualAge, this was accomplished by pressing Ctrl and PF1 to PF3.
In EGL's GUI runtime, this is accomplished the same way. NOTE: This method does not work for the EGL Curses runtime.
In EGL's GUI or Curses runtime, this can also be accomplished by pressing Ctrl-A, then PF1 to PF3.
Informix 4GL applications understand up to 64 function keys. Currently, EGL supports 24 function keys, which the user can send with the same keystrokes that are described above.
The current Informix to EGL Conversion guide outlines a post migration step that involves setting up the build descriptor file for the converted project. This step is no longer required. Rather, a default build descriptor file for the workspace should be created and used.
Starting with the 6.0.1.1 release of the conversion tool, it will not generate the "genProject" and "genDirectory" properties in the build descriptor file. With this change, any build descriptor file generated by conversion tool can be used as default build descriptor.
To set the default build descriptor for the workspace, please refer to the EGL documentation in Help > Help Contents.
To resolve Java threading issues when communicating with non-thread safe Unix curses libraries, the EGL Curses runtime code has been enhanced to provide a more solid synchronization model. As a result, new JNI curses libraries are available to work with the EGL 6.0.1.1 Curses runtime. Previous JNI curses libraries will not work properly with this 6.0.1.1 release. New JNI curses libraries must be downloaded from the Rational download site.
When migrating VA Generator web transactions programs and UI Records to EGL, you cannot do the Stage 2 / Stage 3 migration to a temporary directory. You must migrate to a workspace.
You can assign default values to fields when adding a new row to the Faces Client Components DataGrid at runtime and set the default value to null.
Using the onRowAdd event handler the new EObject for the new row can be intercepted before it is added to the DataGrid:
- Add the onRowAdd attribute to the datagrid tag :
<odc:dataGrid allowRowAddAndDelete="false" styleClass="dataGrid" showSelectionColumn="false" pageSize="10" id="dataGrid1" onRowAdd = "return myOnRowAddHandler( this, event);">- You can then write any JavaScript™ in the handler or use the handler to set the default attributes in the EObject for the new row. This handler will be called when the user tries to add a new row to the DataGrid. This code example sets the value of the AGE field in a sample EObject to null:
myOnRowAddHandler(thisObj, thisEvent) {
//thisObj is DataGrid Control
var objs = thisObj.Adapter.EObjects;
objs[objs.length-1].eSet("AGE",null);
}
An error might occur when you compare and merge model file versions. The following error message is displayed if you encounter this problem: "EMF error occurred while merging resources."
To work around this problem, run validation on the model file versions to ensure that there are no unreferenceable elements; then compare and merge the model file versions again.
The product home page for Rational Software Architect is www.ibm.com/software/awdtools/architect/swarchitect/. For FAQs, lists of known problems and fixes, and other support information, visit the product support page at www.ibm.com/software/awdtools/architect/swarchitect/support/index.html.
© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
The XDoclet Documentation included in this IBM product is used with permission and is covered under the following copyright attribution statement: Copyright (c) 2000-2005, XDoclet Team. All rights reserved.
Portions based on Design Patterns: Elements of Reusable Object-Oriented Software, by Erich Gamma, Richard Helm, Ralph Johnson and John Vlissides, Copyright (c) 1995 by Addison-Wesley Publishing Company, Inc. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this documentation in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this documentation. The furnishing of this documentation does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, JapanThe following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OR CONDITIONS OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:
Intellectual Property Dept. for Rational Software
IBM Corporation
20 Maguire Road
Lexington, MA
02421-3112
USASuch information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.
The licensed program described in this documentation and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.
Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples may include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs.
Each copy or any portion of these sample programs or any derivative work, must include a copyright notice as follows:
© (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. 2004, 2005. All rights reserved.
If you are viewing a soft copy of this information, the photographs and color illustrations may not appear.
Programming interface information
Programming interface information is intended to help you create application software using this program.
General-use programming interfaces allow you to write application software that obtain the services of this program's tools.
However, this information may also contain diagnosis, modification, and tuning information. Diagnosis, modification, and tuning information is provided to help you debug your application software.
Warning: Do not use this diagnosis, modification, and tuning information as a programming interface because it is subject to change.
Trademarks and service marks
The following terms are trademarks of International Business Machines Corporation in the United States, other countries, or both:
- ClearCase
- IBM
- Informix
- iSeries
- Rational
- Rational Rose
- WebSphere
- XDE
- z/OS
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Windows and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both.
Intel and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a trademark of Linus Torvalds in the United States, other countries, or both.
Other company, product or service names, may be trademarks or service marks of others.