<%@ page language="C#" masterpagefile="~/templates/Master0.master" inherits="Page" %>

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

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

Build 501j

Bug Fixes

<% if (he) { %>

Stylus Studio® 2006 Build 501j includes fixes for enhanced stability and performance.

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

Stylus Studio® 2006 Build 501j includes fixes for the following known bugs:

<% } %>

Some user-defined adapters could trigger an ArrayIndexOutOfBoundsException.
The Convert to XML module would sometimes fail to convert files with more than 8192 rows.
The WYSIWYG HTML Editor would sometimes crash if you changed the current Properties window tab while editing a value in the HTML canvas.
Recent Internet Explorer patches would sometimes prevent Stylus Studio from displaying the symbol used to represent repeating elements in the WYSIWYG Editor.

Build 501i

Enhancements

Stylus Studio® 2006 Build 501i includes the following enhancements:

The XML to XML Schema Document Wizard now infers the path for the XML Schema (.xsd file) relative to that specified for the source XML document.
The built-in EDI converter now detects multiple transaction sets in a single EDI file.
Stylus Studio now displays the actual xsl:variable values in the Variables and Watch windows, instead of displaying the string "RTF-VALUE".

Bug Fixes

Stylus Studio® 2006 Build 501i includes fixes for the following known bugs:

XSLT

In the XSLT Editor, switching to the Params/Other tab and then back to the XSLT Source tab could cause duplicate templates to be created in templates drop-down list.
Dragging an element in the XSLT Source tab would sometimes copy, instead of cut, the element; and dropping it would not always result in the expected element being created.
Stylus Studio would sometimes crash after exiting if you opened an XSLT stylesheet in both the XSLT Editor and as an XML document in the XML Editor, and then modified the XSLT.
Templates from included stylesheets were displayed in the XSLT Mapper with an incorrect number of arguments.
Templates displayed in the XSLT Instructions > call-template shortcut menu in the XSLT Mapper are now displayed in alphabetical order.
Input ports for named templates in the XSLT Mapper would revert from red (indicating a value had been provided) to white after previewing the XSLT.
Back-mapping from the Profiler report in the Preview window did not work.
Stylus Studio ignored the Saxon setting to suppress warnings when running a 1.0 XSLT stylesheet (-novw) if you were using Saxon in its basic (not schema-aware) execution mode.
If you processed a stylesheet using the Saxon 6.x processor, Stylus Studio would not display any variables in the Variables window during debugging.
If you processes a stylesheet using the Saxon 8.x processor, by default Stylus Studio performed schema-aware processing with DTD validation..
If you processed a stylesheet using the Saxon 8.x processor, Stylus Studio displayed variable values incorrectly in the Variables window during debugging.
If you processed a stylesheet using the Saxon 8.x processor, Stylus Studio would not display the node set associated with variables in the Variables window during debugging.
Stylus Studio would sometimes truncate error messages when processing stylesheets using the Saxon 8.x processor.

XQuery

Pressing Shift + F11 from inside a function while debugging did not debugger to step out of the code at that point.
Dragging and dropping a document from the Project window into a partially defined DOC() function did not result in a correct URL for that document.
Syntax errors would sometimes cause the debugger to stop processing the XQuery.
If you used an XML document based on a SOAP request as the source document in XQuery Mapper, Stylus Studio did not declare the required namespaces defined in the source.
Pressing F10 while debugging did not correctly step over local functions.
Stylus Studio would sometimes crash if you cancelled a debugging session for an XQuery that used a collection to reference a table.
If your XQuery contained a for loop, it would display incorrect values for the return sequence in the Variables window.
If you created a collection as a source in the XQuery Mapper and then added another source file to the Mapper, Stylus Studio would not use the file as the default input and the Preview operation would fail.
The XQuery Mapper did not always properly interpret default namespaces defined in target documents.
The built-in processor did not automatically output namespace declarations.
XML Schema referenced in a DOC() function sometimes caused Stylus Studio to crash.
The built-in processor would fail to load any module that exported a variable.
The built-in processor's error reporting was imprecise.
Stylus Studio displayed an error if you attempted to expand a variable in a local function while debugging using the Saxon 8.x processor.
Stylus Studio would sometimes crash when opening an XQuery query in the Mapper if the XQuery code contained a variable binding having the xs:type declaration and a positional variable (at $p, for example).

Convert to XML

Ghost cells could appear during some editing operations if there was insufficient space to display the entire Convert to XML Editor.
Spurious Java exception messages were displayed in the Output window when opening a file using the Convert to XML adapter.
Stylus Studio would sometimes display a Java NullPointerException error in the Output window if you tried to open a file using the Convert to XML adapter URL in the URL field of the Open dialog box.
Stylus Studio would sometimes ignore the Omit From setting when it was set to Never, omitting attributes with no values from the output.

Web Services

UDDI registries are no longer supported by IBM, SAP, and Microsoft.
When generating the SOAP request, Stylus Studio would sometimes omit the soap:body parts attribute and the soap:header part attribute.
Stylus Studio would sometimes ignore values entered for a Web Service Call argument until the SOAP request was subsequently edited (at which time previously entered values would appear).

Other

File Explorer — If the Java Virtual Machine (JVM) was not available, Stylus Studio would sometimes crash when right-clicking on a Custom File System.
Xalan — Cancelling a stylesheet being processed using the XalanJ processor would cause error exceptions to be thrown.
XML Editor — If your XML document used multiple namespaces, Stylus Studio could sometimes generate an error if you used the Create Schema from XML Content feature.
Java Code Generation —Stylus Studio would sometimes treat directories starting with "u" as an escaped string, and the resulting generated code would fail to compile.
Java API — Java applications could sometimes hang if background threads threw an exception or terminated.
XML Schema Diagram — Stylus Studio would sometimes incorrectly display drop-down lists for read-only properties, and the list would not close.
URL Builder — After expanding a node in the URL Builder tab of the File Open dialog box, Stylus Studio would sometimes fail to display child nodes on subsequent expansions.

Build 501h

Bug Fixes

Stylus Studio® 2006 Build 501h includes fixes for the following known bugs:

XML Editor

Stylus Studio did not correctly Undo some editing operations performed when the document tree was collapsed.
After using the Wrap Lines feature in the XML Editor, Stylus Studio would sometimes crash after undoing editing operations.
Stylus Studio would sometimes crash when selecting the Text tab after executing a Find operation on the Grid tab.

XSLT

A bug in Saxon 8.6.1 could result in an exception when running the XSLT in Stylus Studio. Build 501h contains a patched version of the Saxon processor.
The Stylus Studio built-in XSLT processor would ignore breakpoints if the file used Macintosh-style new lines (a single \r). This could also cause Stylus Studio to not place the cursor in the appropriate line when a template was selected from the drop-down box in the XSLT Editor.
Stylus Studio would sometimes generate an error when processing XSLT if the Saxon.jar file was in your classpath.
If you were using JDK 1.5 and your XSLT used a Web service file system (ws:///) as input, Stylus Studio would sometimes generate an error when processing the XSLT.

XQuery

Stylus Studio would sometimes crash after dragging a variable to the Watch window.
Stylus Studio would sometimes crash when editing the "let" statement in a FLWOR expression.
The internal XQuery processor would sometimes fail to read documents with deeply nested (160 or more) IF statements.
Stylus Studio would sometimes crash after mapping the output port of a newly created FLWOR block to a target document node and then closing the document.

JAXB

Previously, JAXB command line options were not exposed to the user.
The Output window is now displayed when an error occurs during JAXB code generation.
JAXB code generation now uses JVM command line settings specified on the Java Virtual Machine page of the Options dialog box.

Convert to XML

New converter files (.conv) were not marked as new by Stylus Studio, allowing you to close them without saving new work.
Stylus Studio used to generate an error previewing a file that contained a fixed-width region with no line delimiters, and the last row contained less than the number of bytes specified in the Row Length property.
Converter files (.conv) that were manually edited could sometimes cause Stylus Studio to crash depending on the type of error introduced in the file.
Blank Match Patterns defined for a row were sometimes matched before other defined patterns.
Right-clicking on a field-level node in the schema-tree in the Convert to XML Editor could cause Stylus Studio to crash.

EDI-to-XML Converter

Stylus Studio would sometimes crash when attempting to convert a sub-version of a supported EDI message type.
Stylus Studio would sometimes hang when attempting to convert X12 message types with empty nodes.
Stylus Studio did not generate an XML processing instruction in the output from converted EDI files.
Previously, Stylus Studio did not always correctly flush the buffers if you were using the API to XML to EDI, leaving some data unprocessed.

WYSIWYG

Stylus Studio would sometimes crash if the Base URL for HTML Links Resolution property on the Scenario Properties dialog box was set.
Stylus Studio would sometimes corrupt the XSLT after making a change in the WYSIWYG tab and then switching to the XSLT Source tab.
Stylus Studio would sometimes crash when switching to the WYSIWYG tab if the XSLT contained local variables whose values were instantiated by nested templates.

External Preview — Output previewed in an external application was always sent to the application associated with .htm files, and not the application specified for the file type on the File Types page of the Options dialog box.
Schema Diagram — Documentation node content was lost when the documentation node was moved in the Diagram tab in the XML Schema Editor.
Java Code Generation — If you used the Saxon processor, Stylus Studio would ignore all but the last schema specified on the Validation tab of the Scenario Properties dialog box.
TigerLogic — Previously, if you made an error trying to log in to TigerLogic XDMS, Stylus Studio prevented you from trying again until you restarted Stylus Studio.
Source Control — Certain source control operations run against Jalindi Igloo could cause Stylus Studio to crash.
Creating New Projects — Creating a new project by right-clicking on the project root node in the Project window could cause Stylus Studio to crash if a document was open, but hidden (such as the source XML referenced by an XSLT, for example).
Default Database Connections — Previously, Stylus Studio did not allow you to create a default database connection to DataDirect SequeLink Server.
Web Services — The Web Service Call Composer displays Apache Axis as the default client, even though Stylus Studio defaults to .NET.
File Explorer — If you renamed a folder in the File Explorer window, its files would become inaccessible through the File Explorer.

Build 501f

Enhancements

Stylus Studio® 2006 Build 501f includes support for the following:

Saxon 8.6.1 <% if (!he) { %>XQuery processor and <% } %>XSLT processor
Saxon 6.5.5 XSLT processor
MSXML 6.0 XSLT processor
MSXML 6.0 DOM and SAX XML parsers
.NET 2.0 XSLT processor
Sleepycat Software's Berkeley DB XML version 2.2.8

Bug Fixes

Stylus Studio® 2006 Build 501f includes fixes for the following known bugs:

XSLT

If you ran the XSLT Mapper from the command line without specifying any arguments (struzzo.exe -xsltMapper), Stylus Studio generated an ASSERT error.
The Stylus Studio built-in XSLT processor would sometimes fail to output the correct default namespace definition.
Sense:X auto-complete did not always display globlal variables.
When you selected a region of text in a stylesheet, the shortcut menu did not display an option allowing you to create a template based on it.
Stylus Studio would sometimes prevent the XSLT Mapper tab from opening if the underlying XSLT document was incomplete or invalid.

XQuery

The Stylus Studio built-in processor could not evaluate XPath expressions when an attribute was used as a predicate's argument.
The Saxon XQuery processor did not always properly assign the context item to variables declared at the top level.
The Stylus Studio built-in processor would not accept XQuery replace() functions that used regular expressions.

Convert to XML

If you selected a row element name for editing in the Schema pane of the Convert to XML Editor, and then double-clicked the name, the row element would appear in edit mode and the Set Node and Match Pattern dialog box would appear simultaneously.
The Add Node and Pattern menu item was not always available when it should have been.

Missing Adapter .jar Files — If you used a Stylus Studio adapter that required either the edifact.jar or the x12.jar files and they could not be located, the adapter failed to generate an appropriate error.
Converted/Saved EDIFACT Files— Certain EDIFACT message types generated an error when they were converted to XML and then saved as EDI using the converter.
XML Editor — The XML Editor did not always treat existing comments correctly.
Java File System I/O Error — Stylus Studio would display a null pointer exception if you tried to access the Java File System and a local drive (such as the A: drive) was empty or inaccessible.
XML Diff — The XML Diff Viewer would sometimes crash after opening the target file.
JAXB Support — Complex package names did not always create the proper directory structure when generating Java binding classes.

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

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