1.0 Introduction
2.0 Changes from the previous release
3.0 Limitations
3.1 XSL transformation and debug
4.0 Known problems
4.1 Opening large XML files may cause the workbench to close abruptly
4.2 XML to SQL does not support BLOB, CLOB, and Binary data types
4.3 XML to SQL may throw an SQLException for inappropriate date or time formats
4.4 Generating an XML schema from a database table on Arabic/Hebrew machines
4.5 Generating Test Harness and DAD files for DB2 XML Extender on DBCS machines
4.6 Generating an XML schema from a database table that contains DBCS characters
4.7 Applying an XSL stylesheet with an infinite loop to an XML file
4.8 XML Catalog settings is not recoginized in remote XSL launcher
4.9 Generating XSL for an XHTML template without using the 'Extract XML data from XHTML' option
4.10 Reload does not does not change anything in the RMX and XMX editors
4.11 Validation and unresolved URIs
4.12 Problems using Java Bean XML/XSL Client wizard if bean has methods with the same parameter names
4.13 BiDi encoding problems may be encountered when generating an XML schema or DTD file
4.14 XSL Transform output view empty when tracing remote XML transformation
4.15 Renaming a namespace in an XML schema creates a new namespace
4.16 Painting problems in XML editor
4.17 Encountering external tool error while using the XSL Debugging and Transformation wizard or creating an XML digital signature
4.18 XSL debugger ingores Enabled/Disabled flag on a breakpoint.
The following XML development environment tools are available in WebSphere Studio: XML editor, DTD editor, XML schema editor, XSL editor, XSL debugging and transformation tool, XML to XML mapping editor, and the RDB to XML mapping editor (which you can use to generate DAD files for the DB2 XML Extender). Also included are Java class libraries and wizards for storing and retrieving XML data from any JDBC databases, XML security support, an XPath expression wizard and many generators (such as XML DOM/XSL generation from a Java bean and XSL/XML generation from XHTML file).
The following enhancements have been made for WebSphere Studio Version 5.1:
- New options have been added to the Create XML File wizard
- The XML schema Graph view has been enhanced
- Functionality changes have been made to the XSL Transformation and Debugging tool. You can now run transformations and debugging separately
If path or filename to XML /XSL files has non ascii character, XSL debug and transformation may not function correctly.
Exercise caution when opening large files with any of the XML editors. If the memory limits of the workbench are exceeded, it will abruptly close without saving any data (and without warning or error messages). The number of elements in an XML file, not its size, is the best indicator of how much memory will be required. Memory requirements also depend on what else is open in the workbench - in some cases you can open a 15 megabytes file, but in other cases a one-megabyte file may cause problems. Therefore, we recommend you save all data in the workbench before opening large XML files.
Note: You can change the maximum memory allocated to WebSphere Studio. For more information, refer to the Workbench readme.
XML to SQL does not update the database table properly when the column type is Binary, BLOB, or CLOB. This applies for the INSERT and UPDATE actions.
When updating a database table that has columns with the data type Date, Time, or Timestamp, the XML to SQL wizard or xmltosql and sqltoxml JAR files may throw an SQLException if the string value in the input XML source is not accepted by the target database product. The date and time formats are slightly different from one product to another. You can use the SQL query builder to determine the correct formats of these types.
When generating an XML schema file from a database table, the following error message may be produced in the Tasks pane, especially on Arabic or Hebrew platforms: "Premature end of file."
The schema file will be generated correctly nevertheless. Refresh the target workspace folder that you specified, then open the file with the XSD editor.
If you are generating the test harness files on Windows, the batch files generated use CR as the line delimeter while they should be using CRLF. As a result, the files may not run properly. In this case, insert the line delemiters manually using a text editor such as NotePad.
Also, note that a DAD file should be generated in the platform's default encoding to run properly. You can do this by selecting the proper encoding value from the XML file preferences editor.
If you generate an XML schema from a database table containing full-width alphabet and digit names you will receive errors in the Tasks view. We recommend you do not give database tables and columns names that contain DBCS characters.
If the XSL stylesheet you apply to an XML file to has an infinite loop, you may receive an error message such as the following:
Xalan dies with a java.lang.StackOverflowError,
most likely due to deep recursion.You should fix your stylesheet before you re-run your transformation. If you do not fix the stylesheet and immediately re-run the transformation, you may receive a different error message - this occurs because memory failure can occur in different places in the virtual machine. If this occurs, you should close WebSphere Studio, restart it, and fix the XSL stylesheet to clean things up.
When applying an XSL file against an XML file that includes a DTD or XSD file, any settings that you have in the XML Catalog will be honored if you are launching the XSL Debugger in a local XSL process.
If your XSL file calls external Java beans and you have to launch the XSL Debugger in a remote XSL process, the URI to key mappings in the XML Catalog are not honored and you will receive a java.io.FileNotFound exception.
To work around this, change the XML file so that the included DTD or XSD can be located directly (that is, without going through the XML Catalog).
When data is already stored in an XML file, you would invoke the 'XSL for XHTML template' wizard without selecting the 'Extract XML data from XHTML' option.
Due to a current limitation, the dataLogic file that is generated by the wizard must be hand edited to specify the data related logic specific to the XML file that is the subject of the transformation. Example dataLogic files are included in the 'XML from XSL and HTML' example project.
If you do not hand edit the data related logic file, the XSL files will produce a skeleton HTML file that will not include any data.
The reload option, which is prompted when the contents of an edited file change on disk, does not do anything. This should be noted particularily for Team Support. In the case where a user checks out a file, and the file's contents are different than those in the editor, the editor will prompt the user to reload, but the reload action will not do anything. In this case, you should close down the RMX or XMX session and reopen it to edit the newly checked out file.
The behavior of the XML parser when encountering an unresolvable URI (for example, in a DOCTYPE declaration) is to report a fatal IO error and stop any further processing. An unresolved URI is seen neither as a syntactic nor a semantic error and as such, the parser does not attempt to handle it. Essentially, the document remains unchecked.
For the Java Bean XML/XSL Client wizard if the bean has methods with the same parameter names, the fields for the input form will be generated with the same name as well.
The workaround is to rename method parameters so that there is no name overlap for parameters of the methods that are used for bean generation.
When you generate an XML schema from a DTD file that contains Hebrew or Arabic elements or generate a DTD from an XML schema that contains Hebrew or Arabic elements, certain element names may be encoded with their equivalent hexadecimal Hebrew and Arabic encoding values. To avoid this problem, change the encoding attribute of the original DTD or XML schema file to UTF-8 before performing the generation: That is, the XML declaration should be:
<?xml version="1.0" encoding="UTF-8"?>
The list of affected encoding values is:
- ISO-8859-8-I
- ISO-8859-8
- Windows-1256
- ISO-8859-6
The XSL Transform output view in the XSL debug perspective will not show any output when tracing an XSL transformation launched on a remote application.
If you change the target namespace in an XML schema, a new namespace is created with prefix Q1. To avoid this, first move your global elements and types to the top of the document (before they are actually referenced). Then, apply your target namespace change.
You may experience painting or refresh problems in the XML editor.
If you are using the XSL Debugging and Transformation wizard on Linux and you select Remote XSL application in the Select XSL Launcher page, you may encounter a javaw error.
As well, if you are trying to create an XML digital signature, you may encounter a keytool error.
To work around either of these errors, you must add a path to JAVA_HOME\bin to your PATH environment variable. This path comes from the default JRE specified in Windows > Preferences > Installed JRE preferences (for example, WS_installdir\eclipse\jre\bin).
You can select Enable Breakpoint and Disable Breakpoint from the XSL editor pop-up menu, however, the XSL Debugger ingores the Enabled/Disabled flag on a breakpoint.
Return to the main readme file
(C) Copyright IBM Corporation 2000, 2003. All Rights Reserved.