# 21. Appendix

Chapter Contents | Prev | Next
Keyword Search:
www.openlinksw.com
docs.openlinksw.com
Book Home
Contents
Preface
Appendix
YACC SQL Grammar Reference
Error Codes Reference
Release Notes
New Features Bugs Fixed
Product Support
Virtuoso System Tables
Basic Syntax of Regular Expressions
Server & client versions compatibility

## 21.3. Release Notes

### 21.3.1. New Features

- SOAP 1.1 Implementation - this new release includes a wide range of new SOAP features, bringing it up to date with the most recent developments of this rapidly evolving technology :

- Flexibility in configuring SOAP access points using a WEB based user interface allowing exposure of selected stored procedures as SOAP services. These procedures may be local or linked from any 3rd party databases. The effective privileges for running SOAP exposed procedures can also be set at the access point level.

- Improved SOAP to Virtuoso/PL Language Binding allowing the receiving and returning of arbitrarily complex arrays and structures, using XML Schema to describe the mapping of Virtuoso internal types to precisely match specification expressed in XML Schema.

- Automated generation of WSDL descriptions of SOAP access points - Simple procedure parameter lists map automatically to SOAP types described in XML Schema. For complex types, procedures can be annotated with explicit references to XML Schema types. Thus the developer has complete control over the presentation of web services.

- Import of WSDL descriptions of outside web services. Virtuoso automatically generates Virtuoso/PL wrappers based on an outside WSDL file, making all its services transparently callable as stored procedures from Virtuoso/PL.

- Virtuoso's SOAP client and server implementations pass the SOAP Interop tests levels 1, 2 and most of 3.

- Virtuoso Service Module for XML (VSMX) is a mechanism provided by Virtuoso for testing SOAP messages by automatically generating a test page - a VSMX file - that has the extension .vsmx. The VSMX file is generated at the same time as the WSDL file is generated, giving instant access to your SOAP messages to test they perform as expected. Web Service developers would use VSMX to forego the test bed creation step in light of automatic test page generation. Project managers can easily keep track of their developers progress by checking the test page periodically.

- XSLT 1.1 Implementation - support for the XSLT 1.1 Draft Specification has been added.

- Exposure of Stored Procedures as Web Services - Stored procedures can be exposed as SOAP services very simply from Virtuoso, whether the procedures are native Virtuoso or on remote data sources. This powerful ability means that any database servers already existing within an organization can easily become a component in an eBusiness solution using Virtuoso.

- XML Schema - contains a built-in XML Schema 2001 validator. This is accessible from Virtuoso/PL as a function and is used for SOAP and XQuery where appropriate.

- XML Templates - Virtuoso XML templates allow execution of SQL/XML queries over HTTP to obtain an XML document in response and/or perform some operation in the database using updategrams. The XML Template file can be stored either on the file system, WebDAV repository or stored on another HTTP server being referenced by a URL parameter.

- XQuery - Virtuoso provides support for the XQuery 1.0 XML Query Language specification. This specification is currently in the working draft stage at the W3C XML Query Working Group working in collaboration with the W3C XSL Working Group.

- Web DAV - support for redirection of resources, using the Web DAV Redirect Reference Resource Protocol draft 02 specification.

- Remote Stored Procedures - Stored Procedures located in remote databases can now be linked into the Virtuoso Server in the same manner as you would link in tables or views. This enables remote stored procedures to be readily and easily exposed as WEB Services.

- OLE DB Provider - native OLE DB Provider is now available allowing direct connection from ADO and .Net applications.

- JDBC Driver - enhanced JDBC support with full compliance with JDBC J2EE standard.

- Free Text - The full text indexing capability has been extended, giving the developer flexibility in choosing complex, multi-part document id's for application specific sorting of hits, efficient storage of secondary, non-free text data in the free text index for best retrieval performance, options for restarting searches at a specific hit, ascending and descending orders of document id's and more.

- Free Text Triggers - The free text triggers system allows persisting free text queries into a table, so that when a free text index is updated, the incoming data gets automatically matched against these persisted criteria, generating hits as the index is updated. This allows very high performance filtering of fast changing text data, e.g. news feeds without having to run periodic query batches and is ideal for creating personalized information feeds.

- LDAP - support for the Lightweight Directory Access Protocol (LDAP) protocol for accessing online directory services.

- Enhanced Flexibility of Database and VDB security - New SQL hooks allow the developer to customize password checking at the time of accepting SQL connections into the server. Another hook allows an application to dynamically determine the login/password to use when connecting to a remote database. These hooks make it possible for example to consult an LDAP directory for user information when validating logins.

- File DSN support - with the ability to describe a database connection in a simple disk file, Virtuoso becomes more portable, and no longer dependent on per-machine DSNs. If you use file DSNs you can move your database file and your connection information to any computer that has the appropriate drivers installed.

- Scrollable cursor support in the stored Procedure Language (PL) - Virtuoso PL now allows you direct access to all ODBC standard features of scrollable cursors through PL routines. ODBC calls are still supported but you have a choice of which level to write your code.

### 21.3.2. Bugs Fixed

- Bug 3889 Change label of tab "XML Services/Queues".

- Bug 3891 Admin UI Home Page Update for 3.0.

- Bug 3892 Server Startup Information (Branding Info).

- Bug 3893 When v:data-set @nrows = 1 the 'next' and 'prev' buttons do.

- Bug 3895 Segmentation fault after running dbpump from Yacutia.

- Bug 3907 Explain HO-S-4 and HO-S-5 login.

- Bug 3918 Validators can't work inside Data-Set.

- Bug 3919 There is no way to format columns data in editing controls.

- Bug 3920 v:button @style=url or @style=image not working properly.

- Bug 3921 Logical validators error in Data-Set.

- Bug 3923 xslt_format_number doesnt work properly with value 0.

- Bug 3924 "Cancel" failed after Edit mode in Data-Set.

- Bug 3925 v:column is not more needed in v:data-set.

- Bug 3926 v:update-field obsoleted.

- Bug 3931 Initializing JAVA Hosting Tutorials hangs server.

- Bug 3932 Position Holding in Tutorial Frames.

- Bug 3936 Virtuoso Unix Installer script.

- Bug 3943 Data-Set don't work properly inside 'if-login' template.

- Bug 3950 PDF Version of Documentation is not match HTML.

- Bug 3956 Tutorial Reorganization.

- Bug 3969 Install.sh text changes.

- Bug 3972 Configs, Makefile and installer are not "unpublished propriety.

- Bug 3973 Virtuoso crashes.

- Bug 3984 Dynamic Generation of Runtime Tutorial Heading.

- Bug 3998 bad xpath_eval with //.

- Bug 3999 Group by clause works wrong.

- Bug 4000 end_result() has wrong side effect when procedure called from procedure view.

- Bug 4003 Some catalogs missing in drop down in SOAP expose.

- Bug 4004 Move Reload button in SOAP expose.

- Bug 4005 Rename Grant and revoke buttons in SOAP expose.

- Bug 4006 SQL Error 22023 SR016 in SOAP endpoint hierarchical list.

- Bug 4013 Install.sh conclusion text needs changing.

- Bug 4017 Installer is broken - uid and password update.

- Bug 4021 Lack of pre_render_ method for most of controls.

- Bug 4025 Service Tray Service Manger About contains a typing mistake.

- Bug 4026 UDDI; typo in Contact details tab "Address".

- Bug 4030 DB - TABLE CREATION : Data entered by user is lost.

- Bug 4034 Absence of the strong KEY column for the UDDI.DESCRIPTION t.

- Bug 4044 style="url" for "Delete" v:button in data-set caused error.

- Bug 4049 V:URL unsuitable.

- Bug 4054 WSDL import uncatched error.

- Bug 4062 Virgin XP installation of Mono Based Server fails to start.

- Bug 4063 Installer does not set CLASSPATH to point to Virtuoso JDBC.

- Bug 4066 Virtuoso Java Based Server fails to start.

- Bug 4067 Linux installer does not present best default Server for install.

- Bug 4076 System Tray Icon doe not get removed.

- Bug 4078 gacutil is missing for RT framework.

- Bug 4079 VSCM toggles the wrong DB.

- Bug 4084 Server Crash - ASP.NET hosting.

- Bug 4090 Retrieve in tables list.

- Bug 4095 Browse button in column name for v:text inspector does not work.

- Bug 4096 v:login + page-decor + buttons failed.

- Bug 4099 Problem with ORDER BY.

- Bug 4100 Problems with using xpath_contains and xquery_eval in SQL statement.

- Bug 4102 Kill foreground process misses php java mono servers.

- Bug 4106 SQL-XML unhandled error.

- Bug 4109 DB hang when running backup with clear backup context checker.

- Bug 4110 SQL-XML Error message upon unsuccessful execution of query.

- Bug 4111 SQL-XML Error attempting to reset the form.

- Bug 4114 Virtuoso service starts even though no valid license found.

- Bug 4115 Installer doesn't alert user of non-started instance.

- Bug 4118 case expression incorrectly works in select statement.

- Bug 4125 eNews fails to display scrolling items.

- Bug 4126 Driver does not display SQLSTATE error messages.

- Bug 4129 Views do not show up via SQLTables call.

- Bug 4130 entity reference &nbsp; breaks XSLT processor.

- Bug 4159 Can't insert date/datetime values as string literals.

- Bug 4169 Page with list of saved SQL->XML queries missing.

- Bug 4170 Successful/unsuccessful messages in SQL->XML.

- Bug 4171 SQL-XML misplaced option.

- Bug 4173 Missing owner/group params in SQL-XML page.

- Bug 4174 Missing default root element name in SQL-XML execution.

- Bug 4175 SQL-XML execution Apply XSLT?.

- Bug 4177 Button names in Profiling.

- Bug 4181 Can not "manage" the default "db30" instance.

- Bug 4188 Open Demo.openlinksw.com in New Window.

- Bug 4196 Min And Max attributes for v:validator.

- Bug 4197 v:validator with test="sql".

- Bug 4207 Visit the online tutorials links are inconsistent.

- Bug 4217 Declare continue handler for block don't work.

- Bug 4222 ho-s-7 (DataGrid Demo) problems.

- Bug 4234 Tutorial and offline documentation creation failure in demo.

- Bug 4245 .NET client can't work properly with ODBC driver.

Previous Error Codes Reference | Chapter Contents | Next Product Support