|
Oracle® Containers for J2EE Deployment Guide
10g Release 3 (10.1.3) Part No. B14431-01 |
|
 Previous |
 Next |
|
Oracle® Containers for J2EE Deployment Guide
10g Release 3 (10.1.3) Part No. B14431-01 |
|
|
Previous |
Next |
This chapter discusses redeployment of Web services. It includes the following topics:
A Web service can be packaged as a WAR or as an EJB JAR containing stateless session beans for deployment into OC4J.
Note that if an archive containing a Web service does not include a Web Services Description Language (WSDL) document, OC4J will generate a WSDL document at deployment time.
See Chapter 5, "Deploying Web Modules" for a discussion on deploying and redeploying WAR files into OC4J.
See Chapter 4, "Deploying Enterprise JavaBeans" for guidelines on deploying and redeploying EJB archives.
The deployment plan editor provided with Oracle Enterprise Manager 10g Application Server Control Console includes the ability to set values in the OC4J-specific Web services deployment descriptor (oracle-webservices.xml) at deployment time. See "Setting Web Services Configuration Properties" for details.
In general, the guidelines for updating a Web service in OC4J are the same as those for any WAR or EJB JAR containing stateless session beans.
However, redeployment of a Web service is essentially required when:
Changes are made to the existing reliability configuration
Changes are made to existing security policies or data set in XML configuration files
Redeployment is required so that an updated WSDL document containing the updated reliability and/or security notations can be supplied. Without the updated WSDL document, clients calling the Web service will not work correctly.
Ideally, a new WSDL document containing the updated reliability and/or security notations should be supplied with the WAR or EJB JAR during redeployment. If no WSDL document is supplied, OC4J will generate a new document with the correct notations. However, data set in the previously deployed WSDL document will be lost.
