Release Notes for <%= ConfigurationManager.AppSettings["SS"] %> 2006 Release 3 <%=edition%>

This document contains information specific to the current release of Stylus Studio® 2006 Release 3, Build 653g, as well as all previously released 653 builds. Consult the Stylus Studio Release Notes that are part of the Stylus Studio 2006 Release 3 installation package for other important information.

Build 653g

Bug Fixes

Stylus Studio® 2006 Release 3 Build 653g includes fixes for the following known bugs:

• Support for IE7 Beta — Stylus Studio did not support Internet Explorer 7 Beta and would sometimes crash when previewing transformations.
<% if (!he) { %>
• DB-to-XML Data Sources — Dragging and dropping a relational data source from the File Explorer into a new DB-to-XML data source document would sometimes cause Stylus Studio to crash.
• Java Editor — The Java Editor incorrectly interpreted a quotation mark (") used as a character constant as the start of a character string.
<% } %>

• Stylus Studio would sometimes crash while previewing results.
• The Lookup List in the Convert to XML Editor did not allow you to enter a value if the data was missing in the file you were converting to XML.

• The built-in processor did not return keys in document order.
• Stylus Studio used the built-in processor even if the XSLT document was configured to use MSXML 6.0.
• Using the MSXML 6.0 processor disabled any xsl:include and xsl:import statements by default.

Build 653e

Bug Fixes

Stylus Studio® 2006 Release 3 Build 653e includes fixes for the following known bugs:

• XPath Query Editor — The XPath Query Editor was not evaluating XPath expressions relative to the cursor/selection position in the document being queried.
• Source Control — Stylus Studio would sometimes crash when editing a file under source control.
• FTP Connections — Stylus Studio would sometimes enter a loop if you tried to connect to a non-existent FTP server.
• File Explorer — Under certain conditions, Stylus Studio would sometimes display duplicate server names in the File Explorer window.
<% if (!he) { %>
• DB-to-XML Data Sources — Stylus Studio would sometimes prevent you from saving the result of a DB-to-XML data source (.rdbxml) as an XML document.
<% } %>

• When using the Adapter API, Stylus Studio would sometimes emit a NULL pointer exception if the first adapter referenced in the code was specified using a relative path (./abc.conv, for example).
• Stylus Studio would not allow you to specify adapters using a relative path (./abc.conv, for example) in the Open dialog box.

• Trying to connect to a DB2 database from the RelationalDB folder in the File Explorer window caused an error.
• Stylus Studio would sometimes crash when trying to save an XML document based on a relational database table created by double-clicking the table in the File Explorer window.

• Stylus Studio would sometimes crash when unsimplifying an XML Schema diagram that had been previously simplified.
• The links in XML Schema documentation did not always work when using the XS3P format.

• When the SOAP-encoding definition (xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/) was missing from the WSDL root, Stylus Studio used it as the default namespace in the SOAP request, making the SOAP request invalid.
• SOAP requests generated from multi-part messages were cached incorrectly in Stylus Studio, making the SOAP request invalid.

• Stylus Studio would delete import module functions from the source XQuery document after displaying the document using the XQuery Mapper.
• DB-to-XML data sources (.rdbxml were not always displayed correctly in the XQuery Mapper.
• After selecting one database connection, and then another, and then trying to delete the latter connection from the schema pane in the in the XQuery Editor, Stylus Studio would sometimes delete the first database connection.
• Stylus Studio would sometimes crash if the XQuery being executed used a variable that was defined in a module containing nodes.
• XQuery executed against DB2 databases would fail.

<% if (pe) { %> <% } %> <% if (ee) { %> <% } %> <% if (he) { %> <% } %>

<% if (!he) { %> <% } %>