Home > Stylus Studio Support Center > Update Stylus Studio > Stylus Studio 2007 R2 Release Notes

Release Notes for Stylus Studio® 2007 XML Professional Edition

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

---

Build 894m

Bug Fixes

Stylus Studio® 2007 Build 894m includes fixes for the following known bugs:

XML Editor

• The cursor was not placed on the proper column when identifying the location of an error (non-wellformed XML, for example) in the XML Editor.

XML Schema Editor

• Stylus Studio crashed if you switched to the Documentation tab in the XML Editor when MSXML 4.0 was not installed.

Saxon Processor

• Performance of the Saxon processors for both XLST and XQuery was improved.
• Values in the Watch and Variables windows in the XSLT Editor did not always appear when using the Saxon processor.

XQuery and XSLT Mappers

• Stylus Studio did not always preserve the if/then and sequence constructs.
• The Create Copy Links choice on the short-cut menu that appears when dragging a node from the source to the target using the right mouse button did not always respect the node order defined in the target XML Schema.

---

Build 894k

Bug Fixes

Stylus Studio® 2007 Build 894k includes fixes for the following known bugs:

XML Editor

• The View menu would sometimes not appear after undocking the XPath Query Editor window.
• Stylus Studio would sometimes crash when trying to use the XML Differencing module after using the XPath Query Editor to query an XML document.
• The XML document would sometimes disappear from the Text tab after generating an XML Schema based on that document and then changing to the Schema tab and clicking the Open External Schema button.
• Stylus Studio would sometimes crash when reparsing large (greater than 100Mb) documents to which numerous large document segments had been copied.

XQuery

• Stylus Studio was unable to register SQLServer connections that used Windows integrated security, preventing tables and views from being used as sources for XQuery.
• The XQuery Mapper did not generate code for Java extension functions that was compatible with the DataDirect XQuery processor.
• Static methods of classes in Java extension functions were not always navigable in the XQuery Mapper if the class was inside a package.
• Certain expressions, like div, created in XQuery Mapper would lose the associated curly braces.
• Stylus Studio was not always able to locate functions in external modules that used updating functions.
• In some situations, Stylus Studio would corrupt the attributes and computed expressions of XML literals used in function calls.

XSLT

• Stylus Studio mistakenly performed a copy when using drag & drop operation.
• Stylus Studio would sometimes drop assignments made to text nodes when switching from the Mapper to the Text editor.

---

Build 894i

Bug Fixes

Stylus Studio® 2007 Build 894i includes fixes for the following known bugs:

General

• Stylus Studio Framework — The Automatically add the Base Catalog to New Projects setting on the Application Settings page of the Options dialog box was ignored when opening a file for editing.
• XML Editor — Saving an XML document from the Text Editor after it had been parsed (for presentation in another editor, like the Tree Editor, for example) would result in the loss of any data not previously saved.
• Stylus Studio URI Resolver — The Use Stylus Studio URI Resolver setting on the Processor tab of the XQuery and XSLT Scenario Settings dialog boxes should have been removed in the previous release. Checking this property would sometimes cause Stylus Studio to crash when processing XQuery or XSLT.

XSLT

• If the XPath expression checkbox was selected for a parameter on the Parameter Values page of the Scenario Properties dialog box, then the parameter was not always properly bound if the XSLT used the Stylus Studio built-in or Saxon processor.
• When creating a new XSLT stylesheet using the XSLT Mapper, Stylus Studio did not always correctly create child elements for the <root> element.
• Stylus Studio would sometimes throw an exception if you were processing an XSLT 2.0 stylesheet that used a data type constructor (xs:int(count(//book)), for example).

XQuery

• Stylus Studio did not correctly build URLs for SQL Server named instances, preventing their use as data sources in the XQuery Mapper.
• By default, Stylus Studio fully escaped identifiers when using the DataDirect XQuery processor, which sometimes caused an error for SQL identifiers that started with "xml". Stylus Studio now uses a partial escaping heuristic, but you can always change this using the DataDirect XQuery JdbcSqlXmlIdentifierEscaping data source property when specifying the Server URL property in the Connection Settings dialog box (//localhost:1433;sqlXmlIdentifierEscaping=full, for example). See the DDXQDataSource and DDXQJDBCConnection Properties section in the DataDirect XQuery User's Guide and Reference for more information.
• The syntax highlighting in the XQuery Editor would not succesfully refresh, hanging Stylus Studio, if a token in the XQuery exceeded 16kb.
• Stylus Studio would sometimes crash if the default input URL contained an embedded blank space and you used the Saxon processor to preview the XQuery and your Java Virtual Machine (JVM) was 1.6.x.

Other

• XML Schema — Stylus Studio would crash if you tried to refresh an open XML Schema that had been deleted on the file system.

---