Release Notes for <%= ConfigurationManager.AppSettings["SS"] %> 2010 XML <%=edition%>
This document contains information specific to the current release of Stylus Studio® 2010, Build 1540b,
as well as all previously released 1540 builds. Consult the Stylus Studio Release Notes that are part of the Stylus Studio 2010
installation package for other important information.
Build 1540b
<% if (!ee) { %>
Stylus Studio® 2010 Build 1540b includes ongoing work to improve reliability and performance.
<% } %>
<% if (ee) { %>
Enhancements
- The File Explorer now exposes SYNONYMS for those relational databases that support them.
<% } %>
<% if (ee) { %>
Bug Fixes
Stylus Studio® 2010 Build 1540b includes fixes for the following known bugs:
DataDirect XML Converters
- The Generate XQuery from EDI Standards and Generate XML Schema from EDI Standards document wizards now allow you to select user-defined messages.
- The repeat count in [n:m:r] masks were not always accepted.
- The Generate XQuery/XML Schema feature in the SEF Editor (right-click an EDI message and choose Generate XQuery/XML Schema) ignored settings specified in the SEF file.
- Trying to unlock the .NET XML Converters in a multi-threaded environment sometimes failed.
- EDIFACT message names can now exceed six characters.
- In Custom XML Conversions, records in input files in fixed-width regions that both spanned the input buffer and used a record delimiter character sometimes resulted in the creation of an additional, incomplete XML elements.
- Deeply nested EDI files (for example, groups within groups) could sometimes cause Stylus Studio to run out of memory.
- Custom XML Converters sometimes displayed COMP-3 fields incorrectly if the data came from an EBCDIC file; conversion of the file was unaffected.
- Adding and then removing a reference to a variation to an EDI standard (to a new element, for example) would sometimes cause Stylus Studio to crash.
Other
- Stylus Studio would sometimes generate invalid C# code for XSLT if the Use Stylus Studio URI Resolver property in the XSLT scenario was not selected.
<% } %>
<% if (pe) { %>
<% } %>
<% if (ee) { %>
<% } %>
<% if (he) { %>
<% } %>
<% if (!he) { %>
<% } %>