This section lists the limitations and known issues of this release. It also provides information about any fixes or workarounds that exist for resolving these limitations and issues.
Currency symbol is not validated in CurrencyValidator.
Currency symbol cannot be displayed when bColl is used as a data module.
Type initialize does not report accurate exception messages.
There are multiple validations for an input value and the valid sequence is weird. This is cause by DOJO mechanism.
If a value for the height property of a table is not specified, a user cannot edit the table in Internet Explorer 8.
When defining data mappings, validation exceptions occur during mapping. This is caused by the absence of a validation mechanism when the context.setValuteAt() is called.
AJAX invocation can be launched only by a form.
A direct pagination table does not support the “go to a specific page” function.
Select widget doesn't support duplicate background value due to filter function.
Table widget can not support pagination and editable together
Textbox widget validation sequence may met some problem
In Type.xml, the default type name is like ByteNumber, ShortNumber, FloatNumber, it should be identical in webservice tooling parse mechanism, otherwise, it can't match the data type.
DataMapperExpressionConverterFormat does not support map elements in multiple level list at the same time.
Processor does not add dataElement into an icoll dynamically if the icoll is defined as type.
End user needs to lost focus when submit editable table in IE
Fileupload widget doesn't support multiple files upload.
The XUI editor does not support Linux operating systems.
A .transaction file cannot be imported from a .xml file.
A .xui file cannot be imported from a JSP file.
XUI and transaction template files cannot be saved in a plug-in folder, which is not efficient for sharing.
Classes with inheritance relationship -- This Web services tooling could partly support the generation of classes and WebSphere® Multichannel Bank Transformation Toolkit resources if there is inheritance relationship in WS types definition. In the latest version, the tooling works correctly if all the classes in the inheritance structure are insatiable. The tooling has not been designed to work for the classes which are abstract classes or interfaces.
Multiple embedded collection type -- This Web services tooling could partly support the generation of classes and WebSphere Multichannel Bank Transformation Toolkit resources if there is complex classes composition relationship in WS types definition. But there is an exception if there are more than one collection in the composition relationship. For example, if 'List A' contains 'Bean B', and then 'Bean B' has a field whose type is 'List C', the formatter will be generated into structure as '*.*'. And it is not supported by both Web services runtime and tooling.
Camel case names -- The names of Java resources such as classes, package and fields will be converted into camel case style after the stub class generation. It is the behavior from XJC tool which is used by JAXB implementation. But in our Web services tooling, there are some defects in the camel case conversion imported by wsimport (JDK tool). The conversion result sometimes is different from JavaBean standard. And this defect will cause a problem during the data mapping.
Enumeration and annotation -- Some features such as enumeration and annotation are not supported now in latest version. It means users can not define enumeration and annotation in WSDL types.
In the WebSphere Multichannel Bank Transformation Toolkit Transaction Editor- operation, create a new operation definition; there will be a generated implClass. But when moving the operation class to another package, there's a popup message box ask: Update reference to "operation.java", check this option, but you will find there's no change in implclass for operation definition in transaction editor.
When refer an element which is from an imported definition file, the detail sub fields of the referenced element can not be navigated in editor.
In BTT Transaction Editor- operation, create a new operation definition, there will be a generated implClass. but, When move the operation class to another package, there's a popup message box ask: Update reference to "operation.java", check this option, but you will find there's no change in implclass for operation definition in transction editor.
Property view can not be auto focused once a tooling element is clicked in eclipse environment.
The XUI editor does not support Linux operating systems.
A .transaction file cannot be imported from a .xml file.
A .xui file cannot be imported from a JSP file.
XUI and transaction template files cannot be saved in a plug-in folder, which is not efficient for sharing.
Classes with inheritance relationship -- This Web services tooling could partly support the generation of classes and WebSphere® Multichannel Bank Transformation Toolkit resources if there is inheritance relationship in WS types definition. In the latest version, the tooling works correctly if all the classes in the inheritance structure are insatiable. The tooling has not been designed to work for the classes which are abstract classes or interfaces.
Multiple embedded collection type -- This Web services tooling could partly support the generation of classes and WebSphere Multichannel Bank Transformation Toolkit resources if there is complex classes composition relationship in WS types definition. But there is an exception if there are more than one collection in the composition relationship. For example, if 'List A' contains 'Bean B', and then 'Bean B' has a field whose type is 'List C', the formatter will be generated into structure as '*.*'. And it is not supported by both Web services runtime and tooling.
Camel case names -- The names of Java resources such as classes, package and fields will be converted into camel case style after the stub class generation. It is the behavior from XJC tool which is used by JAXB implementation. But in our Web services tooling, there are some defects in the camel case conversion imported by wsimport (JDK tool). The conversion result sometimes is different from JavaBean standard. And this defect will cause a problem during the data mapping.
Enumeration and annotation -- Some features such as enumeration and annotation are not supported now in latest version. It means users can not define enumeration and annotation in WSDL types.
In the WebSphere Multichannel Bank Transformation Toolkit Transaction Editor- operation, create a new operation definition; there will be a generated implClass. But when moving the operation class to another package, there's a popup message box ask: Update reference to "operation.java", check this option, but you will find there's no change in implclass for operation definition in transaction editor.
When refer an element which is from an imported definition file, the detail sub fields of the referenced element can not be navigated in editor.
In BTT Transaction Editor- operation, create a new operation definition, there will be a generated implClass. but, When move the operation class to another package, there's a popup message box ask: Update reference to "operation.java", check this option, but you will find there's no change in implclass for operation definition in transction editor.
Property view can not be auto focused once a tooling element is clicked in eclipse environment.
The XUI editor does not support Linux operating systems.
A .transaction file cannot be imported from a .xml file.
A .xui file cannot be imported from a JSP file.
XUI and transaction template files cannot be saved in a plug-in folder, which is not efficient for sharing.
Classes with inheritance relationship -- This Web services tooling could partly support the generation of classes and WebSphere® Multichannel Bank Transformation Toolkit resources if there is inheritance relationship in WS types definition. In the latest version, the tooling works correctly if all the classes in the inheritance structure are insatiable. The tooling has not been designed to work for the classes which are abstract classes or interfaces.
Multiple embedded collection type -- This Web services tooling could partly support the generation of classes and WebSphere Multichannel Bank Transformation Toolkit resources if there is complex classes composition relationship in WS types definition. But there is an exception if there are more than one collection in the composition relationship. For example, if 'List A' contains 'Bean B', and then 'Bean B' has a field whose type is 'List C', the formatter will be generated into structure as '*.*'. And it is not supported by both Web services runtime and tooling.
Camel case names -- The names of Java resources such as classes, package and fields will be converted into camel case style after the stub class generation. It is the behavior from XJC tool which is used by JAXB implementation. But in our Web services tooling, there are some defects in the camel case conversion imported by wsimport (JDK tool). The conversion result sometimes is different from JavaBean standard. And this defect will cause a problem during the data mapping.
Enumeration and annotation -- Some features such as enumeration and annotation are not supported now in latest version. It means users can not define enumeration and annotation in WSDL types.
In the WebSphere Multichannel Bank Transformation Toolkit Transaction Editor- operation, create a new operation definition; there will be a generated implClass. But when moving the operation class to another package, there's a popup message box ask: Update reference to "operation.java", check this option, but you will find there's no change in implclass for operation definition in transaction editor.
When refer an element which is from an imported definition file, the detail sub fields of the referenced element can not be navigated in editor.
In BTT Transaction Editor- operation, create a new operation definition, there will be a generated implClass. but, When move the operation class to another package, there's a popup message box ask: Update reference to "operation.java", check this option, but you will find there's no change in implclass for operation definition in transction editor.
Property view can not be auto focused once a tooling element is clicked in eclipse environment.
The XUI editor does not support Linux operating systems.
A .transaction file cannot be imported from a .xml file.
A .xui file cannot be imported from a JSP file.
XUI and transaction template files cannot be saved in a plug-in folder, which is not efficient for sharing.
Classes with inheritance relationship -- This Web services tooling could partly support the generation of classes and WebSphere® Multichannel Bank Transformation Toolkit resources if there is inheritance relationship in WS types definition. In the latest version, the tooling works correctly if all the classes in the inheritance structure are insatiable. The tooling has not been designed to work for the classes which are abstract classes or interfaces.
Multiple embedded collection type -- This Web services tooling could partly support the generation of classes and WebSphere Multichannel Bank Transformation Toolkit resources if there is complex classes composition relationship in WS types definition. But there is an exception if there are more than one collection in the composition relationship. For example, if 'List A' contains 'Bean B', and then 'Bean B' has a field whose type is 'List C', the formatter will be generated into structure as '*.*'. And it is not supported by both Web services runtime and tooling.
Camel case names -- The names of Java resources such as classes, package and fields will be converted into camel case style after the stub class generation. It is the behavior from XJC tool which is used by JAXB implementation. But in our Web services tooling, there are some defects in the camel case conversion imported by wsimport (JDK tool). The conversion result sometimes is different from JavaBean standard. And this defect will cause a problem during the data mapping.
Enumeration and annotation -- Some features such as enumeration and annotation are not supported now in latest version. It means users can not define enumeration and annotation in WSDL types.
In the WebSphere Multichannel Bank Transformation Toolkit Transaction Editor- operation, create a new operation definition; there will be a generated implClass. But when moving the operation class to another package, there's a popup message box ask: Update reference to "operation.java", check this option, but you will find there's no change in implclass for operation definition in transaction editor.
When refer an element which is from an imported definition file, the detail sub fields of the referenced element can not be navigated in editor.
In BTT Transaction Editor- operation, create a new operation definition, there will be a generated implClass. but, When move the operation class to another package, there's a popup message box ask: Update reference to "operation.java", check this option, but you will find there's no change in implclass for operation definition in transction editor.
Property view can not be auto focused once a tooling element is clicked in eclipse environment.