Enhancements to Liquid Data Control in WebLogic Workshop.

The Liquid Data Control is now distributed and available directly from WebLogic Workshop. Previously, the Liquid Data Control was installed into Workshop as part of the Liquid Data installation process.

Using Liquid Data Controls to Develop Workshop Applications in the Application Developer's Guide

Dynamic Data Sources

You can now optionally specify the data sources for XML files and delimited files at query runtime.

Configuring Access to Delimited Files and Configuring Access to XML Files in the Administration Guide; and xs:document in the XQuery Reference Guide

Improvements to the Data View Builder

There are many improvements to the Data View Builder, including more efficient query generation and look-and-feel improvements.

Building Queries and Data Views

Data Source Status Checks

Liquid Data now includes checks of the status of Liquid Data objects in the Administration Console.

Checking the Status of Liquid Data Objects in the Administration Guide

Improvements to Query Processing and View Performance

There are performance improvements for many query use cases, including queries that involve views.

Documentation Improvements

There are numerous updates to the Liquid Data documentation, including revisions to the Building Queries and Data Views and a new book entitled XQuery Reference Guide.

Liquid Data EDOCS Web Site

Liquid Data Control in WebLogic Workshop.

You can now create Liquid Data Controls in WebLogic Workshop to build applications that use data from Liquid Data queries.

Using Liquid Data Controls to Develop Workshop Applications in the Application Developer's Guide

Delimited files as data sources.

You can now use delimited files as data sources to use in queries.

Configuring Access to Delimited Files in the Administration Guide

Improved management of stored queries.

You can now add simple or complex input parameters to data views.

Configuring Stored Queries in the Administration Guide

Improvements to the Data View Builder.

There are many improvements to the Data View Builder, including mapping lines and the ability to deploy queries and views directly from the Data View Builder.

Building Queries and Data Views

Security enhancements.

Liquid Data supports WebLogic Server security policies, which allow you to create security rules for objects that are dynamically evaluated at runtime.

Security in Liquid Data in the Administration Guide

Query Cache APIs.

There are now APIs to programmatically purge entries from the query cache.

Using the Cache Purging APIs in the Application Developer's Guide

SQL query as a data source.

You can now write vendor-specific SQL queries and use them as data sources in Liquid Data.

Defining Stored Procedures and SQL Queries in Building Queries and Data Views

Enhanced query plan caching.

Query plans for ad-hoc queries are cached to enhance performance of applications using ad-hoc queries.

Building Queries and Data Views

Stored procedures.

You can now access stored procedures defined in relational databases without requiring the use of database adapters.

Defining Stored Procedures in Building Queries and Data Views

Complex parameter types.

You can now define user-defined complex parameter types which take an XML data stream as an input.

Using Complex Parameter Types in Queries in Building Queries and Data Views

Parameterized views.

You can now add simple or complex input parameters to data views.

Using Data Views as Data Sources in Building Queries and Data Views

Multiple levels of data views over data views is fully supported.

You can now create as many levels of data views as you need. (Previously only one layer of abstraction was possible.)

Using Data Views as Data Sources in Building Queries and Data Views

Enhanced namespace support in the Liquid Data server.

Liquid Data now supports XML Namespace declarations in queries and schema.

Understanding XML Namespaces in Building Queries and Data Views

Security with the JSP tag library.

There are now username and password attributes for the query JSP tag library, allowing you to specify a WebLogic username and password to use for your query.

Invoking Queries in JSP Clients in the Application Developer's Guide

Ability to edit the target schema in the Data View Builder.

There is now enhanced support of editing target schemas in the Data View Builder. For example, you can specify the data type and namespace of attributes and elements.

Building Queries and Data Views

Internationalization support.

Liquid Data supports multi-byte data from the underlying data sources.

Internationalization Support in the Installation Guide

Domain Configuration Wizard enhancements.

You can now configure domains with Liquid Data and other BEA products directly through the WebLogic Domain Configuration Wizard.

Deployment Tasks in the Liquid Data Deployment Guide

Informix database support.

Liquid Data now supports access to Informix databases.

Supported Databases and Drivers in the WebLogic Platform documentation.

CR081983

Use of xfext:time-from-dateTime function in a query result shows a time that is one hour behind the actual time.

Problem

When you use the xfext:time-from-dateTime function in XQuery for a query, the XML query result will show a time that is one hour behind the intended time.

Platform

All

Workaround

This is a known Java Virtual Machine (JVM) bug from Sun Microsystems, Inc. (logged as ID: 4414844). As a workaround, add one hour to the time of day value when you build the query.

CR082881

The floor, ceiling, and round functions have problems handling large numbers.

Problem

The xf:floor, xf:ceil, and xf:round functions do not handle large numbers correctly.

Platform

All

Workaround

For large numbers (larger than 2147483647 and smaller than -2147483647), do not use xf:floor or xf:ceil. Use the function xf:substring(<large_number>,".") for floor and Use the function xf:substring(<large_number>+1,".") for xf:ceil.

CR087058

The Liquid Data installer overrides the beahomelist file.

Problem

If you are using a NIS/NFS based file system and have Liquid Data installed on multiple systems, each time you run the installer it will rewrite the beahomelist file. The existing BEA homes from the previous install will not be listed in the new beahomelist. (The most recent installation will have its BEA home in the list and it will be the only one listed.)

Platform

All platforms when using NIS/NFS-based file system with Liquid Data installed on multiple systems.

Workaround

Edit the beahomelist file to include the appropriate BEA homes.

CR087410,
CR087443

Removing a generated Web Service from the Liquid Data web_services_gen directory does not automatically remove it from the WebLogic Server (WLS) Web Services table as expected.

Problem

When a generated Web Service is removed from the Liquid Data repository web_services_gen directory, it is undeployed and removed from the directory. At this point, Liquid Data console management should also automatically remove the Web Service from the Web services table in the WLS Administration Console. But the Web Service is not automatically removed—it still shows up in the WLS Web Services table even after removal from the web_services_gen directory.

Platform

All

Workaround

Follow these steps to remove a generated Web Service for a stored query in Liquid Data:

1. Use Administration Console to browse the web_services_gen directory in the Liquid Data server repository. (Click the Liquid Data node in the Administration Console, then click the Repository tab.)

2. Click the trash can icon (Delete) next to the EAR file for the generated Web Service that you intend to remove and confirm.

3. On the left pane of the Administration Console, click the Web Service Components folder to display the table of WLS Web service components.

4. In the table, click the trash can icon (Delete) next to the EAR file for the generated Web service that you removed earlier from Liquid Data and confirm.

CR091944

The Monitor tab in the Liquid Data Administration Console does not appear in a clustered configuration.

Problem

When Liquid Data is deployed in a cluster, the statistical data in the Liquid Data > Monitor tab disappears from Liquid Data console.

Platform

All

Workaround

None available.

CR096240
CR096331

Unsupported JDBC type found when running an existing query on Oracle RDBMS.

Problem

When using the Oracle 9.2 JDBC driver with Oracle 8.1.7, some queries might fail with unsupported JDBC data type errors.

Platform

All

Workaround

If you are using Oracle 8.1.7, use the Oracle 8.1.7 JDBC driver; if you are using Oracle 9i, use the Oracle 9.2 JDBC driver.

For details on changing the JDBC driver, see http://download.oracle.com/docs/cd/E13222_01/wls/docs81/jdbc/thirdparty.html#1043614

CR096974

Changes to Liquid Data configuration may adversely affect the ability of WebLogic Server to restart after a server failure.

Problem

The following condition can occur:

• While WebLogic Server is running, a change is made in Liquid Data configuration.

• The change may contain an error of some type.

• The WebLogic Server fails.

• A reboot of the server cannot be fully effected due to an error in the Liquid Data configuration.

Platforms

All

Workaround

The Liquid Data environment should be frequently exported. This is especially true when configuration changes are made such as adding, removing, or updating a data source.

Using a recently exported configuration, the workaround for the problem described above is to:

Remove the entire contents of the LDdomain/userConfig directory, including any sub-directories.
Start the server for the domain.
Set the location of the domain LDrepository directory to the value you originally configured. For details see the Server Repository Location discussion in the Liquid Data Administration Guide.
Import Liquid Data configuration information. See Importing and Exporting Liquid Data Configurations in the Liquid Data Administration Guide.

CR099042

In IBM DB2, when returning a result set from a stored procedure, connections are not being released.

Problem

When using the IBM DB2 Type 3 JDBC driver to access stored procedures, connections are not always released, which can cause subsequent queries to fail. This is a problem in the DB2 Type 3 JDBC driver.

Platform

All

Workaround

Use the IBM DB2 Type 2 JDBC driver; the Type 2 driver does not have this problem, and releases the connections as expected.

CR099523

Undeploying/Deploying the LDS.ear file sometimes requires the user to log back into WLS to gain access to the Liquid Data Administration Console.

Problem

If you undeploy the LDS.ear application from the WebLogic console, when you redeploy the application, you might need to log back into the console in a new session in order to see the Liquid Data Administration Console node in the WebLogic console.

Platform

All

Workaround

Start a new console session by exiting your browser and logging into the Liquid Data Administration Console again.

CR100052

Cannot project an element that is not mapped in the underlying view.

Problem

When you create a data view in Liquid Data, you must map all elements and/or attributes to the target schema. That is, every element in the target schema must have a valid mapping. If you do not map all of the elements and attributes, queries against the resulting view might fail.

Platform

All

Workaround

Map all elements and attributes to the target schema (even if they are optional) when creating data views.

CR100708

Liquid Data console hangs if you are using the Sun 1.4.1_01 Java plugin in your browser.

Problem

If you are using the Sun 1.4.1_01 Java plugin in your Internet Explorer or Netscape browser, accessing the Liquid Data console will hang your browser and might hang the machine in which the browser runs.

Platform

All

Workaround

Do not use the Sun 1.4.1_01 JVM; upgrade to the Sun 1.4.1_02 or later JVM from java.sun.com.

CR101650

If NVARCHAR2 Oracle Column is passed to Function eq() and "Query Parameter", SQLException will occur.

Problem

Using Oracle 8.1.7 with the 8.1.7 JDBC driver, if you pass an NVARCHAR2 column with a Query Parameter argument to the xf:eq function, a SQLException occurs.

Platform

All

Workaround

If you encounter this problem, use one of the Oracle 9i JDBC drivers.

CR101658

Japanese filenames do not display in the repository Administration Console.

Problem

If files are stored in the Liquid Data repository with Japanese filenames, they cannot be configured correctly with the Liquid Data Administration Console.

Platforms

All

Workaround

Do not use Japanese characters in your repository directory or file names.

CR101921

Cannot process xs:short, xs:byte stored procedure input parameter.

Problem

When mapping numeric constants to the stored procedure inputs that contain input parameters of type xs:byte and xs:short, you must explicitly cast the constant to the type xs:short or xs:byte, respectively, or an error will occur.

Platform

All

Workaround

When you map any constants to input parameters of type xs:byte and xs:short in stored procedure queries, you must first explicitly cast the constants to xs:byte and xs:short, respectively.

CR102004

Informix stored procedure hangs with no result coming back.

Problem

Due to a problem in the Informix JDBC driver, when executing a stored procedure against an Informix data source, the query can hang without returning any results.

Platform

All

Workaround

When using stored procedures with Informix data sources, set the Prepared Statement Cache Size to 0 in the JDBC Connection Pool used in the data source. The Informix JDBC driver does not behave properly when using stored procedures with a cache size greater than zero. This will not impact the performance of the stored procedure because Stored Procedure statements are not cached. BEA recommends creating two different JDBC connection pools for Informix data sources, one for stored procedures and another for Table access. Set the Prepared Statement Cache Size property to a non-zero value for the Table access JDBC pool and set it to zero for the Stored Procedure access JDBC pool.

CR102072

Cannot select NCHAR Column with oracle9iR2.

Problem

You cannot select NCHAR columns with Oracle9iR2. The following error message occurs when trying to select an NCHAR column: "Error: Unable to parse the result."

The release notes from the Oracle Patch Set 92021 has the following description of this problem:

Bug 2285052 Fixed: 9202

JDBC Nulls are being padded instead of blanks when selecting a NCHAR column when using thin JDBC with some database character sets.

Platform

All

Workaround

If you are using Oracle 9i with NCHAR columns, install the Oracle patch 92021.

CR102469

Cannot use Japanese repository directory name.

Problem

If you try to enter a name for the Liquid Data repository that contains Japanese characters (from the Administration Console —> Liquid Data —> Configuration tab —> General tab —> Repository Directory), a configuration error occurs.

Platform

All

Workaround

Do not use Japanese character in your repository directory name.

CR102652

Liquid Data does not handle the target namespace defined in the WSDL properly, resulting in overloading problems.

Problem

When using multiple web services as data sources, it is possible to have namespace collisions where Liquid Data cannot differentiate between the two web services.

Platform

All

Workaround

When designing WebLogic Workshop web services, you may need to alter the targetNamespace for a web service if a method name in this web service clashes with a method name in another web service that uses the same targetNamespace.

CR108344

Liquid Data RDBMS Data Source against Oracle 7.3.4 fails with Oracle 9 JDBC Drivers

Problem

If you use one of the Oracle 9 JDBC drivers to access an Oracle 7.3.4 database and you create a Liquid Data Data Source that accesses that JDBC data source, the data source initialization fails.

Platforms

All

Workaround

If you are using Oracle 7.3.4, use the Oracle 8.1.7 JDBC driver instead of one of the Oracle 9 JDBC drivers/

CR110103

Some Oracle JDBC drivers report DATE columns as DATETIME.

Problem

Certain combinations of Oracle JDBC drivers and servers incorrectly report the type of DATE columns as DATETIME, therefore Liquid Data treats them as DATETIME.

Platforms

All

Workaround

If you encounter this problem, add a cast as xs:date function in your query to the DATETIME column results to cast the DATETIME values to DATE.

CR110502

License manager not always using the newest license for Liquid Data.

Problem

If you have multiple Liquid Data licenses in the license.bea file, the license manager might not use the latest license.

Platforms

All

Workaround

Whenever you update the Liquid Data license in the license.bea file, remove any older Liquid Data license entries from the license.bea file, leaving only the newest entry.

Platforms

All

Workaround

Ignore these warning messages.

CR111137

Cannot create elementFormDefault="qualified" attribute in the Data View Builder.

Problem

You cannot create schemas with the elementFormDefult="qualified" attribute/value pair in the Data View Builder. If you need a schema with this attribute/value pair, create the schema outside of Data View Builder and then you can set the target schema to it and generate an XQuery using that schema.

Platforms

All

Workaround

If you need to use schemas with the elementFormDefult="qualified" attribute/value pair, create the schema outside of Data View Builder and the use Set Target Schema to specify the schema in the Data View Builder.

CR111214

Schema URLs for import and include statements must resolve or web service generation will fail.

Problem

If you are generating a web service with Liquid Data, any import and include statements in the schema file for the stored query must have a URL that can be resolved by the WSDL parser. Local filenames or relative URLs will not resolve in the generated web service.

Platforms

All

Workaround

Do not use local filenames in import/include statements for target schemas. Make all import and include statements in a target schema resolvable over http, ftp, or some other network protocol available to the web service.

CR111288

If the IP address changes while the Liquid Data server is running on the local machine, connecting to some data sources with the Data View Builder fails.

Problem

If you are running Data View Builder and the Liquid Data server locally on the same machine and if your IP address changes (for example, if you start up Liquid Data and the Data View Builder on a laptop connected to one network, then put the laptop in sleep mode and reconnect it to another network), you might not be able to use the Data View Builder to access certain data sources, and the Data View Builder will fail with the following error:

java.io.StreamCorruptedException

Platforms

All

Workaround

If you encounter this situation, restart the Liquid Data domain and reconnect with the Data View Builder.

CR112353

Package contains no type of this name error after changing the query many methods access in an existing JCX file.

Problem

If you edit several methods in rapid succession in an existing Liquid Data Control (.jcx) file to change the queries they access (using the Property Editor wizard accessible from the right-click menu on a method), in some rare cases it is possible to get in a situation where the methods in the JCX file cannot find the XMLBean classes they return. Saving your files, restarting WebLogic Workshop, and updating the Liquid Data Control file corrects the problem.

Platforms

All

Workaround

If you encounter this problem, save your work, restart WebLogic Workshop, and update the Liquid Data Control as described in Updating an Existing Liquid Data Control if Schemas Change in the Liquid Data Application Developer's Guide.

CR112367

NetUI does not generate the input form correctly for queries with input parameters of xs:dateTime. xs:decimal, xs:integer, or xs:time.

Problem

If you use WebLogic Workshop NetUI to generate a page flow JPF file from a Liquid Data control and include queries with input parameters having types xs:dateTime. xs:decimal, xs:integer, or xs:time, then the input form generated must be modified for inputs of these types.

Platforms

All

Workaround

In the JSP file with the input form(s), the inputs with these types include a message similar to the following:

To-Do: To create an input form for a complex data type (java.sql.Timestamp), open the page editor and add netui input tags for the relevant fields of the class.

You can treat these types of input parameters as strings. To work around this, substitute code similar to the following for the data cell corresponding to the input parameter:

<td>
  <netui:textBox dataSource="{actionForm.endDate}"/>
</td>

where actionForm.endDate corresponds to the XMLBean class member for the input parameter.

CR123193

In Data View Builder, projects that contain Web Service complex mappings from web services returning arrays might return element names different from the target schema.

Problem

Web Services returning arrays do not provide information about the name of each element in the arrays returned. While this is valid in WSDL, it is not supported by XML Schema. To overcome this limitation, Data View Builder assigns the name "item" to all such not-named elements. If you map (copy & paste with map) such an array from the output of the web service to the target schema, Data View Builder carries over the name "item" to the expanded target schema. However, the web service, when called, returns elements most likely not named "item". This means that the result of the query would not match the target schema. This can be an issue when you deploy the query or view and specify a target schema.

Platforms

All

Workaround

If you run into this issue, edit the target schema so that the element names match those returned by the web service. Note that you must modify the target schema outside of the Data View Builder project, because you cannot modify the name of a mapped element in Data View Builder. Use the edited target schema for deploying the query and/or view, but not in the Data View Builder project.

CR123410

Inconsistent source schema view using different DB2 JDBC drivers.

Problem

The data direct DB2 JDBC driver returns a different schema from the IBM type2 driver for DB2 7.2. The data direct driver returns the schema and catalog name; the IBM driver does not.

Platforms

All

Workaround

If you have built queries using the IBM DB2 JDBC 7.2 driver and now want to use new BEA JDBC driver. you must specify a unique schema name and catalog name in the Liquid Data data source configuration. Then the queries will run as before.

CR124404

Sybase and Microsoft stored procedures do not work with Liquid Data when using the BEA Sybase JDBC driver.

Problem

The BEA JDBC drivers for Sybase and Microsoft SQL Server do not properly transform the stored procedure name needed by the Liquid Data server. This causes errors similar to the following to occur:

error occurred while evaluating the function urn:SY-WL:CallInOutWithResultSet_1. (com.enosysmarkets.exceptions.UserException: Query Execution Error (Stored Procedures) 1-2-6-11: Could not get callable statemement from resource 'SY-WL'. (java.sql.SQLException: [BEA][Sybase JDBC Driver][Sybase]Incorrect syntax near '{'.) (java.sql.SQLException: [BEA][Sybase JDBC Driver][Sybase]Incorrect syntax near '{'.

Platforms

All

Workaround

If you are accessing stored procedures in Sybase or Microsoft SQL server databases, use the JDBC drivers supplied by the vendor instead of the BEA JDBC drivers for those databases.

CR125712

Server does not support concurrent access to PointBase databases.

Problem

If the Shared Connection attribute is set for a Liquid Data data source that accesses a PointBase database, concurrent queries will fail with an internal error.

Platforms

All

Workaround

Do not set the Shared Connection attribute for Liquid Data relational data sources that access PointBase databases. Make sure the Shared Connection box is not checked in the Configure a Relational Database Data Source Description page of the Liquid Data Administration Console for data sources accessing PointBase databases.

CR125786

Sybase JConnect 5.5 JDBC driver returns incorrect results for "output" parameters of DECIMAL data type.

Problem

The Sybase JConnect 5.5 driver does not return the proper output value for stored procedures "output" parameters of DECIMAL type.

Platforms

All

Workaround

Use the BEA Sybase JDBC drivers for these types of stored procedures or use the Sybase JConnect 4.5 driver.

CR126222

A query must not return a NULL value (it must return at least an empty root element) for web services generated from a Liquid Data Control where the query returns no results.

Problem

If you generate a Web Service from a Liquid Data Control in WebLogic Workshop, and the control accesses a query that returns no results (returns a NULL value), WebLogic Workshop throws a runtime exception because it encounters a NULL value. The exception is similar to the following:

com.bea.wlw.runtime.core.request.ResponseValidationException: com.bea.xml.marshal.XmlEncodingException: Null value encountered where XML schema requires a value

Platforms

All

Workaround

If you encounter this problem, modify the query so that, in the case that there are no results from the query, it still returns an empty root element (not a NULL value). For example, begin the query with the XML markup for opening the root element (for example, <root>) and end it with the closing tag (for example, </root>).

CR130311

Sample domain does not start after installing Liquid Data over an existing Liquid Data installation.

Problem

If you install Liquid Data over an existing Liquid Data installation (without first uninstalling the old installation), the Liquid Data sample domain will not start unless you delete the following file:

<weblogic_home>/samples/domains/liquiddata/wliconfig/WLI8.1.2_db_tables_checked

Platforms

All

Workaround

Do not install Liquid Data over an existing Liquid Data installation without first uninstalling the old installation. If you encounter this problem, however, you can work around it by deleting the following file from the Liquid Data sample domain:

<weblogic_home>/samples/domains/liquiddata/wliconfig/WLI8.1.2_db_tables_checked

where weblogic_home is the directory in which the WebLogic platform is installed (for example, c:\bea81\weblogic81).

After deleting this file, you can then start the Liquid Data sample domain.

CR130461

A query will return incorrect results if it calls a DataView that returns an empty (null) document.

Problem

It is possible to create a data view in the Data View Builder that will return an empty document (as opposed to an empty root element). However, results returned froma query that invokes a Data View returning an empty document will not be correct.

Platforms

All.

Workaround

If you encounter this problem, modify the stored query which is the basis of the data view so that it will return an empty root element (in other words, it will not return a null value) even in the case that there are no results from the query.

For example, begin the query with the XML markup for opening the root element (for example, <root>) and end it with the closing tag (for example, </root>).