Oracle9iAS Web Services

Release Notes

Release 2 (9.0.2) for UNIX

April 2002

Part No. A96200-01

This document summarizes the differences between Oracle9iAS Web Services and its documented functionality.

1 General Issues and Workarounds

This section describes general issues and their workarounds for Oracle9iAS Web Services.

1.1 Web Services with Java Beans as Parameters

When Java Beans are used as parameters to Oracle9iAS Web Services, the client code should use the generated Bean included with the downloaded client proxy. This is because the generated client proxy code translates Simple Object Access Protocol (SOAP) structures to and from Java Beans by translating SOAP structure namespaces to and from fully qualified Bean class names. If a Bean with the specified name does not exist in the specified package, the generated client code will fail.

However, there is no special requirement for clients who use generated Web Services Description Language (WSDL) to form calls rather than the client proxy. The generated WSDL document describes SOAP structures in a standard way. Application development environments, such as JDeveloper, which work directly from WSDL documents can correctly call Oracle9iAS Web Services with Java Beans as parameters.

1.2 Web Service Assembler and Stored Procedure Web Service

The WebServiceAssembler configuration file does not have a unique tag name for Stateless Stored Procedure Web Service. However, when the <database-jndi-name> element is used inside a <stateless-java-service> tag, the assembler will generate configuration information related to the Stateless Stored Procedure inside the web.xml file.

Oracle is a registered trademark, and Oracle9i is a trademark or registered trademark of Oracle Corporation. Other names may be trademarks of their respective owners.