Table 11 Known Product Limitations and Possible Workarounds
|
|
|
CR265965 (revised Feb. 2, 2007)
|
Updating or deleting Oracle's CHAR/NCHAR with trailing blanks failed using Oracle JDBC driver.
|
|
|
With Oracle's non-XA JDBC driver, CHAR and NCHAR columns can only be updated if the number of characters is 1024 or less. The following message typically appears if this problem occurs:
java.sql.SQLException: ORA-01461: can bind a LONG value only for insert into a LONG column
|
|
|
All, using Oracle's non-XA JDBC driver.
|
|
|
Whenever possible use BEA's Oracle JDBC driver (Type 4).
|
|
|
An exception occurs if a timestamp with time zone is fetched before LONG_RAW.
|
|
|
|
|
|
When using an Oracle database, if a timestamp with a time zone is fetched before a LONG_RAW a "... Stream has already been closed" exception occurs. This is consistent with the way Oracle handles LONG_RAW fetched before blob and clob.
|
|
|
Reverse the fetch order of timestamp with time zone and LONG_RAW when using Oracle.
|
|
|
When executing a SQL query containing a single parameter through the AquaLogic Data Services Platform JDBC driver, a "wrong parameter type" occurs.
|
|
|
|
|
|
When a SQL query is executed, a parameter list containing one and only one parameter is treated as a table parameter instead of a normal parameter, resulting in an exception being returned.
|
|
|
Create a SQL table with a single row contain the parameter value and pass that table parameter to the query. For detailed informations on table parameter s and creating a TableParameter class object see the topic "Table Parameter Support" in the
Using SQL to Access Data Services chapter of Application Developer's Guide.
|
|
|
Importing two or more procedures that have the same return type into an existing data service may not succeed.
|
|
|
|
|
|
An exception can occur when importing multiple data service procedures, if two or more of the procedures have the same return type.
|
|
|
Import procedures having the same return type using separate import operations.
|
|
|
When publishing a WSDL generated from AquaLogic Data Services Platform to the AquaLogic Service Registry, multiple entries may appear for the same WSDL.
Similarly, when configuring a Web service from the AquaLogic Service Registry through the Excel Add-in, multiple entries for the same WSDL may be seen.
|
|
|
|
|
|
When a JWS is generated, by default the form-get and form-post flags are set to True. This setting in conjunction with the absence of a source directive (CR268183) cause multiple entries to appear.
|
|
|
Using the Property Editor in WebLogic Workshop, set the form-get and form-post flags to False. Then, if the goal is to generate a WSDL for Excel Add-in use, the following entry should first be placed at the beginning of the comments in the JWS source file:
* @editor-info:link autogen-style="stateless" source="<jcxfilename>.jcx" autogen="true"
|
|
|
When importing or synchronizing metadata with an Oracle database, the native width of float elements may be incorrectly calculated.
|
|
|
All, using the BEA Oracle JDBC driver.
|
|
|
When importing or synchronizing metadata with an Oracle data source, the width of float elements may be rendered incorrectly (15 instead of 6 or 9). This problem has been observed when using the WebLogic JDBC Oracle driver (version 3.0.5.0).
|
|
|
Metadata synchronization using Oracle's native JDBC driver (Oracle.jdbc.driver.OracleDriver) did not exhibit this problem. Therefore, if the width of native float elements is an issue use the Oracle JDBC driver.
|
|
|
When working with DSP Transport in the AquaLogic Service Bus Console while using a multibyte character set (such as Japanese), unexpected characters may appear in editing fields.
|
|
|
|
|
|
When using the AquaLogic Service Bus Console in conjunction with a DSP Transport Configuration, if the Request Encoding field or the Response Encoding field is set to utf-8 (the default value) unexpected characters may appear in editing fields when using multibyte character sets.
|
|
|
When editing any field in a DSP Transport Business Service configuration, if the request encoding or response encoding should be any value other than the default (utf-8), the setting must be reset to their correct values before saving the configuration.
|
|
|
AquaLogic Data Services Platform functions accessed through a 9.2-level Data Service control via a Java Web service may not successfully execute.
|
|
|
|
|
|
This problem can occur due to differences in the way Web service templates are generated under WebLogic 8.1 and Weblogic 9.2 The template that is generated by a WebLogic Service 9.2 test browser expects a qualified schema and therefore adds namespace prefixes to all elements in the schema. For details see: CR288104 Details.
By contrast, the schema associated with the WebLogic 8.1-level data service does not have elementFormDefault set, so it defaults to unqualified. However, the WebLogic 9.2 Web service sends a qualified xml fragment, causing an error when the schema is passed to the AquaLogic Data Services Platform server running under WebLogic 8.1.
|
|
|
Users working with Weblogic 9.2-level Web services should replace the template generated by the WebLogic 8.1 test browser with the template generated by the WebLogic 9.2 test browser. Alternatively, generated code can be edited to include the XMLBean values in the method before passing it to the AquaLogic Data Services Platform control method.
|
|
|
Duplicate names are allow when mapping stored procedures to data services during metadata import.
|
|
|
|
|
|
The SQL name mapping user interface may allow more than one stored procedure with the same name to be configured under the same schema. However, if more than one stored procedure with the same name is configured, the user will see unexpected results in the JDBC metadata API and on execution of the procedures via JDBC.
|
|
|
In the Publish Data Service Functions for SQL Use wizard, manually rename stored procedures so that there are no duplicate names.
|
|
|
Undetected classname collisions in a Workshop application can cause compilation errors.
|
|
|
|
|
|
This problem can occur when compiling schema files into SDOs using AquaLogic Data Services Platform. If an element or attribute has the same name (such as `sequence') as an SDO reserved method (such as `getSequence( )'), SDO will — through the XMLBean Java code generator — attempt to "uniqueify" the method by generating `getSequence2', as an example.
Here is a list of SDO keywords which could contribute to such name collision conditions:
-
getBoolean, getByte, getChar, getDouble, getFloat, getInt, getLong, getShort, getBytes, getBigDecimal, getBigInteger, getDataObject, getDate, getString, getList, getSequence
-
setBoolean, setByte, setChar, setDouble, setFloat, setInt, setLong, setShort, setBytes, setBigDecimal, setBigInteger, setDataObject, setDate, setString, setList, setSequence
|
|
|
To use the uniqueified name:
- Add a copy of
sdo.xsdconfig to your schema project and
- In your Java file correct the entry to the uniqueified name as in:
addrLine.setSequence2(1);
|
|
|
Excel Add-in will initially attempt to reuse HTTP basic authentication login credentials for all Web services hosted on the same port.
|
|
|
|
|
|
In cases where multiple Web services are configured in a single Excel worksheet, and these Web services are hosted by the same host machine and port number, the Excel Add-In will initially attempt to reuse the previously accepted username/password for these services.
If the username/password is not valid for a particular Web service, a login dialog will be displayed. Subsequent Web service invocations during the same Excel session will use the correct login information for each service.
|
|
|
No action has to be taken, unless it is not deemed acceptable that an attempt is made to authenticate a web service call initially with incorrect credentials.
In such cases Web services requiring different credentials should be grouped in different servers OR Web services requiring different credentials hosted on the same host/port should be used on separate Excel worksheets.
|
|
|
When using AquaLogic Data Services Platform with AquaLogic Service Bus, `dsp' is not supported for inbound transport.
|
|
|
|
|
|
A null pointer exception occurs if you choose dsp type when creating a proxy service in AquaLogic Service Bus. This is because the data service option erroneously appears in the list of available transport types for this kind of operation.
|
|
|
Avoid selecting the dsp type from available options when creating a proxy service in AquaLogic Service Bus.
|
|
|
Several underlying WSDL Element definition attributes and Attribute definition attributes are not currently supported in the AquaLogic Data Services Platform Excel Add-in.
|
|
|
|
|
|
The following Element definition attributes are currently unsupported:
-
substitutionGroup
-
default
-
fixed
-
form
-
abstract
-
block
-
final
The following Attribute definition attributes are currently unsupported:
-
default
-
fixed
-
form
-
abstract
-
block
-
final
|
|
|
Any WSDL containing the definition attributes listed above may not function as expected. If problems are encountered, remove these definition attributes from your WSDL.
|
|
|
For data service files that are large and slow to compile, you may need to adjust the compiler.delay flag to improve response time during source editing.
Consecutive key strokes during source editing are batched into a single compile event. If file compilation is slow, then you may want to adjust the time window for batching key strokes for compilation.
|
|
|
|
|
|
When editing large files in Source View, editing during compilation may cause multiple compilations to occur.
|
|
|
Adjust the compiler.delay environment variable (in milliseconds) to increase the delay between compilations when doing editing. This property should be specified in the workshop.cfg file as a `-D' parameter.
|
|
|
When creating a Data Service control under WebLogic 9.2, an error can occasionally occur if the editor of the Server View is open at the same time.
|
|
|
|
|
|
When generating or editing a Data Service control on Weblogic 9.2, it is recommended that the editor of the Server View not be open.
|
|
|
When generating or editing a Data Service control, if you need to test the JWS, use the:
Run as  Run on Server
option on the right click menu. This option deploys/undeploy the user component.
If, in rare cases, the control fails to undeploy, then access the Web-based Weblogic administration console and perform the required operation from there.
If the aforementioned editor is already open and you want to edit/generate a Data Service control, first close the editor and then restart WebLogic Workshop.
|
|
|
Exception when publishing a WSDL from a data service when an underlying schema does not have a targetNamespace defined.
|
|
|
|
|
|
An exception indicating that you cannot map a prefix when no namespace is present may occur when attempting to generate a WSDL file from a valid data service.
This is due to the fact that one or more schemas that are depended upon by the data service do not have a targetNamespace defined.
|
|
|
Make sure that all schemas underlying your data service have a proper targetNnamespace defined.
|
|
|
When accessing data from Informix, use the Informix native JDBC driver when possible.
|
|
|
All using Informix database systems.
|
|
|
The WebLogic Informix JDBC driver is less performant than the native Informix JDBC driver when accessing data through AquaLogic Data Services Platform.
|
|
|
No workaround necessary, but for best performance with Informix data use its native JDBC driver.
|
CR284534 (updated: 7 June 2007)
|
Unclear exception message when using a Data Service control with WebLogic 9.2.
|
|
|
|
|
|
When using a Data Service control with Weblogic 9.2, if the wls90interop.jar that is required to be on the AquaLogic Data Services Platform Top level is not used correctly, a runtime exception may occur. The exception will appear similar to:
weblogic.rjvm.PeerGoneException: ; nested exception is: java.io.EOFException
|
|
|
If you see such an exception, check the ALDSP 2. x server log. If an error such as the following appears:
java.io.InvalidClassException: javax.xml.namespace.QName; local class
incompatible: stream classdesc serialVersionUID = 4418622981026545151, local class serial VersionUID = -9120448754896609940
then the cause of this error is likely due to one of the following:
- the
wls90interop.jar file is not in the ALDSP 2.x server classpath
- the wls90interop.jar file is not listed first in the classpath.
|
|
|
When using a data service based on a Web service at runtime, a validation error may occur if form and/or elementFormDefault do not match. This happens because redefinition of the `Form' attribute is not supported.
|
|
|
|
|
|
- The elementFormDefault attribute in the primary schema does not match the elementFormDefault attribute in an imported or included schema, or
- if the form attribute of an element does not match the elementFormDefault attribute in the primary schema.
then, at runtime, validation errors will occur when accessing Web service-based data services.
|
|
|
The elementFormDefault in the primary schema and any imported or included schemas should match prior to compilation. Also, the form attribute of the element should match the elementFormDefault in the primary schema.
|
|
|
The Data Lineage feature in AquaLogic Data Services Platform administration console requires the X11 graphical environment in Linux and UNIX environments.
|
|
|
|
|
|
"java.lang.NoClassDefFoundError: sun/awt/X11GraphicsEnvironment"
may occur while accessing the Data Lineage feature of AquaLogic Data Services Platform Administration Console. The circumstances arise when the Administration Server hosting AquaLogic Data Services Platform Administration Console is running on a Linux or UNIX host with one of the following conditions (not an exhaustive list):
- A headless environment is in use — for example, without monitor and/or X server.
- With a monitor, but the user running the administration server is not the same user logged-in from the monitor, and therefore, does not have display permissions to the default display (:0.0).
|
|
|
To resolve this issue, set the headless property to true:
in the Weblogic Server startup script ( startWeblogic.sh) in the section of the script where the server is started.
|
|
|
Unable to add criteria to SQL when using MS Excel with EasySoft or OpenLink.
|
|
|
|
|
|
In Microsoft Query, adding a query criteria using the Add Criteria window, (Criteria Add Criteria) throws an error message when accessing AquaLogic Data Services Platform data sources.
|
|
|
To workaround this issue:
- In the Microsoft Query window, select the Records menu option. If the Automatic Query option is checked, then clear this option.
- Click ViewCriteria. This will add a Criteria window to the query window into which you can enter appropriate criteria.
- To execute query with the criteria added, click Records Query Now.
|
|
|
Cannot use the WLS Administration Console to define a security policy for accessing the AquaLogic Data Services Platform Console.
|
|
|
If a user defines a security policy in WebLogic admin console for AquaLogic Data Services Platform console ( ldconsole.ear), only the user in the Administrator role can access/login to the AquaLogic Data Services Platform console. Other read-only roles (Operator, Monitor, Deployer) fail to access to AquaLogic Data Services Platform console, instead returning the error:
Authentication Denied
The username or password has been refused by WebLogic Server.
|
|
|
|
|
|
By default ldconsole is allowing access ONLY to administrator group. Only when security policy is defined, are other users allowed per defined security policies.
The operation can be completed using the following steps:
- Log in to the WLS console with admin credentials.
- Created a new user (such as JACK_BLACK).
- Assigned the user to the Monitors group.
- Log out of the WLS console.
- Log in to ldconsole in the Admin role.
- Edit security settings in the AquaLogic Data Services Platform metadata browser to add a security policy allowing read access to users of group "Monitors".
- Log in to the ldconsole page using the JACK_BLACK user credentials.
|
|
|
Under some conditions a data service project deployment fails with an error similar to:
Deployment failed, Last Message from the server ...
|
|
|
Under some conditions the weblogic-application.xml can become corrupted when deploying a AquaLogic Data Services Platform-enabled application, leading to a AquaLogic Data Services Platform deployment failure.
|
|
|
|
|
|
A software patch is available at:
Alternatively, performing a Clean operation before a project Build automatically repairs the file:
weblogic-application.xml
|
|
|
Metadata synchronization update preview displays "Problem in parsing XML fragment" error.
|
|
|
If your project contains Java function signatures referring to XMLBeans, then erroneous results may be reported when doing a metadata update.
|
|
|
|
|
|
Delete the <project.jar> file in your application's library folder that was created when you last built your project. Then synchronize and rebuild.
|
|
|
String comparison operations involving MS-SQL may return incorrect results when the comparison operation is computed by MS-SQL.
|
|
|
|
|
|
|
|
|
|
|
|
When importing AquaLogic Data Services Platform projects into Workshop if the option Copy into Application Directory is not selected, importing a project not already located in the application results in `resource not found' errors.
|
|
|
AquaLogic Data Services Platform requires that projects be contained in the application folder. This is handled automatically if the Copy into Application Directory option in Workshop is selected.
|
|
|
|
|
|
Select the Copy into Application Directory option when importing AquaLogic Data Services Platform Console projects.
|
|
|
When casting xs:decimal from an xs:integer or xs:long, resulting values may not be precisely correct.
|
|
|
|
|
|
|
|
|
To avoid the possibility of an incorrect result use a string literal instead of an xs:integer literal. For example instead of:
|
|
|
An exception during an SDO update operation can occur if the order of elements in the client diffgram is changed and the Validate option is active.
|
|
|
Sometimes the order of elements in a diffgram changes, potentially leading to datagraph validation failure.
|
|
|
All, using ADO.NET clients.
|
|
|
If possible, turn off validation for the operation.
|
|
|
Workshop removes a necessary line when editing an AquaLogic Data Services Platform Control-generated JWS file.
|
|
|
After creating a AquaLogic Data Services Platform control it may be necessary to edit the generated JWS file. For example, in the case of enabling Web service security, the user may need to modify the JWS property that specifies a Web service security file.
If the JWS is edited in Workshop, a line in the header beginning:
is automatically removed. This line is needed in order to generate ADO.NET-enabled WSDL files.
| Note: |
This problem also affects the Excel Add-in. |
|
|
|
|
|
|
Before editing a generated JWS file in Workshop open the file in a text editor and copy the line beginning:
Then, when editing the file in Workshop, restore the above line to the JWS file.
|
|
|
SDO does not support periods [ . ] in element names and schema paths.
|
|
|
SDO is dependent on XPath which supports indexing from 0. For example, SDO's Customer.0 equals XPath's Customer[1]. Since periods are already used for this type of notation, they cannot appear in element names.
A more general statement of the problem is that SDO does not support periods in schema paths, including leaf elements.
|
|
|
|
|
|
Avoid using periods in element names and schema paths.
|
|
|
When no values are passed during an insert operation, the generated query contains a null, which can lead to an exception on the database side.
|
|
|
Default values for SDO properties are always null. When no values are passed during an insert operation, the generated SQL insert contains a null. This can lead to an exception of the following form on the database side:
java.sql.SQLException: ORA-01400: cannot insert NULL into ("COMMON"."CASE"."CREATE_USERNM")
The reason this exception occurs is that when metadata is created for database tables, the default value of the database setting is not captured in SDO. So, for example, if the value of the column is "not null" in the database and the SDO datagraph passed a null value to the database, the exception will occur.
|
|
|
|
|
|
Default values should be set in the SDO client.
|
|
|
End-point name changes do not take effect for operations in document style Web services.
|
|
|
Document style Web services use input (call parameter) types to determine the Web service operation being invoked. The operation name is not included in the SOAP request. For this reason, overwriting the operation name as part of an end point change does not work for document style Web services.
|
|
|
|
|
|
|
|
|
Obscure error message when changing Web service end-point settings if an incorrect operation name is used.
|
|
|
"javax.xml.rpc.JAXRPCException: Unable to find operation 'null' in port 'AVP2Port'. Please check the WSDL"
most likely means that an invalid operation name has been selected.
|
|
|
|
|
|
Find correct operation name and change end-point settings accordingly.
|
|
|
Security decisions are not audited.
|
|
|
XQuery functions supporting security are not tracked by the audit framework.
|
|
|
|
|
|
|
|
|
Use of Java keywords in schema elements and namespaces may cause name conflicts.
|
|
|
Schema elements and namespaces are converted into Java classes and packages as part of schema compilation process. This creates the potential for name conflicts with Java keywords and constructs.
|
|
|
|
|
