Stylus Studio® 6 Release 3 (Build 377o)
Recent Changes and Fixes

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

Changes and Fixes in Stylus Studio 6 Release 3 Build 377o

The following changes are introduced with Build 377o:

Bug Fixes

Stylus Studio® 6 Release 3, Build 377o includes fixes for the following known bugs:

• XSLT Mapper
• If you opened an XSLT without any meta knowledge and switched to the Mapper tab, Stylus Studio displayed an error message. This has been fixed in the current build.
• Stylus Studio would sometimes crash if you attempted to delete an invalid reference to the source or target schema. This has been fixed in the current build.
• Stylus Studio would erroneously display a message if you added an XML Schema and that XML Schema referenced a missing XML Schema. This has been fixed in the current build.
• XQuery Mapper — When selecting a node in the text pane of the XQuery Mapper required the currently selected node to change, Stylus Studio would move the editing focus to the Mapper pane. This has been fixed in the current build.
• Collections and Database Connections — If you created a collection that used both default and user-defined database connections, Stylus Studio would generate an invalid database configuration file. This has been fixed in the current build.
• Schema Diagram — The Schema Diagram would crash if you tried to convert a global type into a local type and the global type was undefined. This has been fixed in the current build.
• XSLT Editor — In Stylus Studio® 6 Home Edition, if you changed the stylesheet version attribute from 1.0 to 2.0 and then accepted the prompt to use the Saxon 8 processor, Stylus Studio would automatically select the Use Stylus Studio URI Resolver for the XSLT scenario, even though that option is not available in Home Edition. This has been fixed in the current build.
• Write Access to %ALLUSERSPROFILE% Required — If the user did not have write access to the Windows %ALLUSERSPROFILE% folder, Stylus Studio would crash when the user tried to start the application. This has been fixed in the current build.

Other Changes

The Microsoft .NET XSLT processor requires .NET Framework 1.x. If you have only .NET Framework 2.x installed on your machine, Stylus Studio displays an error message when you execute XSLT using Microsoft .NET.

Changes and Fixes in Stylus Studio 6 Release 3 Build 377n

The following changes are introduced with Build 377n:

Enhancements

We are pleased to announce that Stylus Studio 6 XML Enterprise Edition provides support for DataDirect XQuery™. Support for DataDirect XQuery in Build 377n includes the following:

• The DataDirect XQuery processor is available on the Processor tab of the XQuery Scenario Properties dialog box.
• Support for the collection( ) function. As implemented by DataDirect, the collection( ) function takes a collection (a name that represents a specific database table or view and the server configuration settings needed to access it) as its argument, which allows you to query a relational database table or view on the server. Collections are also supported by other XQuery processors in Stylus Studio, but implementations of the collection( ) function are vendor-specific. The Saxon processor, for example, specifies that the collection( ) function takes a URL as its argument. You can also use the collection( ) with the Stylus Studio built-in processor. In this case, however, the relational data is first converted to XML and queried on the client.
• The Java Code Generator (select XQuery > Generate Java Code from the Stylus Studio menu) generates DataDirect XQuery™ for Java, which is based on the XQuery API for Java™ (XQJ; JSR 225).

Bug Fixes

• XQuery
• Stylus Studio would sometimes crash if you switched from the XSLT Source tab to the Mapper tab while editing the XSLT source code. This has been fixed in the current build.
• Stylus Studio would sometimes throw a NullPointerException when debugging using the Saxon 8x processor if no input document was specified in the XQuery scenario. This has been fixed in the current build.
• Stylus Studio would sometimes add argument ports to function blocks, even if the function was defined as having no inputs. This has been fixed in the current build.
• XSLT
• Changes to the XSLT code made in the Mapper would sometimes cause Stylus Studio to lose the // in XPath expressions (in xsl:for-each instructions, for example). This has been fixed in the current build.
• When running or debugging XSLT stylesheets using the Saxon 8.x processor, Stylus Studio would display diagnostic messages in the Output window, even when TRACE was disabled. This has been fixed in the current build.
• The Java Code Generator did not always successfully resolve URLs specified in document instructions. This has been fixed in the current build.
• XQuery and XSLT Debugging — The symbol used to identify processors for which XQuery and XSLT debugging in Stylus Studio is not supported has been changed.
• XQuery and XSLT Mapper — Stylus Studio did not correctly create namespace prefixes for target nodes when using an XML Schema as a target document. This has been fixed in the current build.
• Java Debugger — Stylus Studio would sometimes crash if you tried to exit Stylus Studio while the Java debugger was stopped at a breakpoint. This has been fixed in the current build.
• Web Service Call Composer — Stylus Studio would sometimes crash when you saved a new Web service call if the Java Virtual Machine (JVM) was disabled. This has been fixed in the current build.
• XML Diff Editor — Stylus Studio would sometimes crash when displaying two or more XML documents on the Split View - Text tab of the XML Diff Editor. This has been fixed in the current build.
• Stylus Studio Custom File System API — Classpaths built by the StylusFileFactory class used the backward slash (\), which did not work in UNIX environments. This has been fixed in the current build.
• XML Schema Documentation — Stylus Studio would use the value of the baseURL property for the XS3P documentation style for the DEFAULT_DOCUMENT_EXTENSION as well. This has been fixed in the current build.
• Open dialog box — If you tried to create more than two new folders using the New Folder button on the Open dialog box, Stylus Studio would stop after the second new folder. This has been fixed in the current build.

Changes and Fixes in Stylus Studio 6 Release 3 Build 377m

The following changes are introduced with Build 377m:

Bug Fixes

• XML Schema
• The keyboard focus in the Text Editor was not retained when switching back to Stylus Studio from other applications. This has been fixed in the current build.
• Links to graphics in generated XML Schema documentation would not function on case-sensitive Web servers. This has been fixed in the current build.
• Error messages would sometimes display incorrect column/row coordinates when reporting unresolved Import statements. This has been fixed in the current build.
• Stylus Studio could not always find the paths specified for imported and included XML Schemas when displaying an XML Schema on the Documentation tab using the XS3P stylesheet. This has been fixed in the current build.
• XQuery
• The XQuery Mapper would sometimes crash when trying to render a Mark Logic XQuery. This has been fixed in the current build.
• Stylus Studio would sometimes crash when stepping through code during debugging if a runtime error occured while the Variables window was open. This has been fixed in the current build.
• XSLT
• Stylus Studio would sometimes crash when adding a new target document to an existing XSLT in the Mapper. This has been fixed in the current build.
• The built-in XSLT processor did not use the updated version of the XSLT stylesheet when the stylesheet was refreshed. This has been fixed in the current build.
• XQuery and XSLT Mapper
• The Find feature did not have useful default settings. Find now searches elements and attributes by default.
• If the Hide Links for Nodes That Are Not Visible feature was enabled for a file displayed in the Mapper and that file was also open in an external application, Stylus Studio would sometimes crash if the file was saved in that application. This has been fixed in the current build.
• XML Grid Editor — The XML Grid Editor could sometimes appear to hang or respond very slowly when displaying documents with large and/or numerous CDATA sections. This has been fixed in the current build.
• DTD Editor — Stylus Studio would sometimes crash if you clicked on the Root node in the Property window. This has been fixed in the current build.
• Java Code Generator — The Java Code Generator available in Stylus Studio 6 XML Enterprise Edition would use short 8.3 path names instead of the full ones. This has been fixed in the current build.
• WYSIWYG Editor — Stylus Studio did not always normalize the first tag name when displaying XSLT in the WYSIWYG Editor (which requires that the output be rendered as HTML). The resulting mismatch (‹BODY› versus ‹/body›, for example) would prevent the XSLT from being previewed in the WYSIWYG Editor. This has been fixed in the current build.

Changes and Fixes in Stylus Studio 6 Release 3 Build 377k

The following changes are introduced with Build 377k:

Enhancements

We are pleased to announce the following enhancements with Build 377k:

• XQuery and XSLT Mapper

The XQuery and XSLT Mappers have several new features that simplify working with complex XQuery and XSLT code:

• Mapper Canvas Filter — The Mapper canvas now has a filter function that allows you to display links only for those nodes that are currently visible on the Source and Target document panes. As you scroll the document panes, bringing new nodes into view, links associated with those nodes, if any, appear on the Mapper canvas. If a node is linked, but its partner node is not visible in the other document pane, Stylus Studio draws a small green arrow next to the node name to show that a link is associated with the node. The button for the Mapper canvas is located in the Mapper tool bar.
  
  You can also select a node from a document pane and, using the shortcut menu (right-click on a node), display only the links associated with that node.
• Search — A new Find feature (right-click on a node) lets you search the Source and Target document panes for a specific node. You can limit your search to elements and/or attributes, and you can search using regular expressions.
• Integration with Raining Data® TigerLogic® XDMS

  Stylus Studio 6 XML Enterprise Edition is now fully integrated with Raining Data TigerLogic XDMS. This means that you can

• Connect to a server hosting a TigerLogic XDMS file system and access XML documents stored in TigerLogic XDMS collections. You can also write well-formed XML documents back to existing TigerLogic XDMS collections.
• Use the TigerLogic XDMS XQuery processor to process your XQuery. Stylus Studio's Sense:X syntax coloring and auto-completion fully supports TigerLogic XDMS syntax.

Bug Fixes

• XML Editor
• Copying XPath to the clipboard would sometimes result in the last character being truncated when pasted. This has been fixed in the current build.
• Stylus Studio would sometimes crash if you refreshed the Tree tab after the document had been updated in an external application. This has been fixed in the current build.
• Stylus Studio would sometimes crash if the Tree tab was active when you associated the XML document with an XML Schema (XML > Associate XML with Schema). This has been fixed in the current build.
• File Explorer
  • The Refresh action did not always restore the plus signs to empty file system folders after they were expanded and their content was then modified (a file was written to them, for example). This has been fixed in the current build.
  • The Refresh action did not always work correctly on expanded folders. This has been fixed in the current build.
  • Clicking the plus sign for the Relational DB file system folder did not always display the Connection Settings dialog box to allow you to define a database connection. This has been fixed in the current build.
  • Setting the filter to a wildcard (*.log, for example) would result in the .conv files being hidden from view in the Convert to XML Definitions folder. This has been fixed in the current build.
  • The Create Folder action did not work when used on a disk root (c:\, for example). This has been fixed in the current build.
  • The list of adapters displayed by the File Explorer did not always agree with the list of adapters in the Select XML Converter dialog box. This has been fixed in the current build.
  • The File Explorer did not always correctly expand shortcut folders. This has been fixed in the current build.
• XQuery
• Stylus Studio could sometimes crash when deleting an attribute from the target schema in the XQuery Mapper. This has been fixed in the current build.
• The links to attribute nodes in XQuery Mapper did not always generate code. This has been fixed in the current build.
• The XQuery engine did not support function overloading — functions with the same name, but different numbers of arguments. This has been fixed in the current build.
• Generating JAXB Classes — Stylus Studio would sometimes crash if you selected the Add generated classes to current project option when generating JAXB classes from an XML Schema. This has been fixed in the current build.
• XQuery and XSLT Mapper — Stylus Studio would incorrectly merge two elements with the same name defined in different namespaces. This has been fixed in the current build.
• XSLT WYSIWYG — xsl:value-of statements coded inside repeating loops would sometimes be moved outside the loop when previewing the XSLT. This has been fixed in the current build.
• Convert to XML — If the .conv file had an empty input tag, Stylus Studio would crash when you tried to open it. This has been fixed in the current build.
• .NET Validator — The .NET Validator always assumed the XML documents it validated used an XML Schema, even if the document used a DTD. This has been fixed in the current build.
• EDIFACT Adapters — If the XML used an EDIFACT feature that let the author of the message omit default values, the XML would validate against the schema generated from the EDIFACT to XML Schema wizard, but it could still convert to invalid EDIFACT. This has been fixed in the current build.
• DB-to-XML Data Sources — If the result from the SQL or SQL/XML query contained any characters that were out of the ASCII range, the resulting XML document would be invalid. This has been fixed in the current build.

Stylus Studio® 6 Release 3 (Build 377o) - stylusstudio_latestfixes_web.htm