Java Web Services Developer Pack 1.3

JavaTM Web Services Developer Pack 1.3 Release Notes

Contents

Supported Platforms
Redistributable Components
Nonredistributable Components
Environment Variables
Modifying Tomcat's and Xindice's Default Host and Port Settings
Modifying the Default Logging Level
Uninstalling Java WSDP 1.3
Known Issues

The JavaTM Web Services Developer Pack (Java WSDP) is an all-in-one download containing key technologies to simplify building of Web services using the Java 2 Platform. For release notes for these technologies see:

Updated, online versions of the release notes are available here.

Supported Platforms

This release of the Java WSDP has been tested in various configurations with J2SE SDK versions 1.4.1_xx and 1.4.2_xx on the following platforms:

Redistributable Components

Redistribution of the entire Java WSDP is subject to this license.

The following Java WSDP components are individually redistributable. Redistribution of a component entails the redistribution of all files comprising the component and any dependent components.

Redistributable Component Files
JAXP jaxp-api.jar, dom.jar, sax.jar, xalan.jar, xercesImpl.jar, xsltc.jar
JAXB * JAXB JAR files (jaxb-api.jar, jaxb-impl.jar, jaxb-libs.jar, jaxb-xjc.jar), JAXP 1.1 or higher JAR files (jaxp-api.jar, sax.jar, dom.jar, xalan.jar), JWSDP Shared JAR files (jax-qname.jar, namespace.jar, xsdlib.jar, relaxngDataype.jar)
JAX-RPC jaxrpc-api.jar, jaxrpc-impl.jar, jaxrpc-spi.jar, relaxngDatatype.jar, xsdlib.jar, JAXP, SAAJ, jcert.jar, jnet.jar, jsse.jar
SAAJ saaj-api.jar, saaj-impl.jar, jaxp-api.jar, dom.jar, sax.jar, xalan.jar, xercesImpl.jar, activation.jar, mail.jar, servlet.jar
JAXR jaxr-api.jar, jaxr-impl.jar, jaxb-api.jar, jaxb-impl.jar, jaxb-libs.jar, saaj-api.jar, saaj-impl.jar, jaxp-api.jar, dom.jar, sax.jar, xercesImpl.jar, activation.jar, jaas.jar, mail.jar, namespace.jar, relaxngDatatype.jar, xsdlib.jar
*  If the application will not be doing any compilation at runtime, the jaxb-xjc.jar file does not need to be redistributed with the application.

Click here to check for any changes.

Nonredistributable Components

The following Java WSDP components are not redistributable. These components can only be used for designing, developing, and testing purposes.

Nonredistributable Component Files
Registry Server registry-server.war, xindice.jar
Java XML & Web Services Security all
JSF all
JSTL all
WS-I Sample Application all
Tomcat all

Click here to check for any changes.

Environment Variables

The JAVA_HOME environment variable is set to point to the version of the J2SE SDK you specify during installation. If you change your J2SE SDK installation, you will need to edit your <JWSDP_HOME>\jwsdp-shared\bin\setenv.bat batch file or <JWSDP_HOME>/jwsdp-shared/bin/setenv.sh and reset the JAVA_HOME environment variable.

All other custom system properties can be set in the file <JWSDP_HOME>/conf/jwsdp.properties as follows: 

http.proxyHost=webcache 
http.proxyPort=8080

You can override any of the properties in your file <JWSDP_HOME>/conf/jwsdp.properties by using the -D... argument to any of the start scripts. For example,

Unix: catalina.sh -Dhttp.proxyHost=webcache -Dhttp.proxyPort=8080

Microsoft Windows: catalina -Dhttp.proxyHost=webcache -Dhttp.proxyPort=8080

Modifying Tomcat's and Xindice's Default Host and Port Settings

By default, Tomcat uses port 8080. There may be times when you need to change this setting. To start Tomcat on a nonstandard port, edit the following portion of the <JWSDP_HOME>/conf/server.xml file, changing the default "8080" value (shown in bold below) to the new port number: 

  <!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->
       <Connector className="org.apache.coyote.tomcat5.CoyoteConnector"
             port="8080" minProcessors="5" maxProcessors="100"
             enableLookups="true" redirectPort="8443" acceptCount="100"
             debug="0" connectionTimeout="20000" 
             disableUploadTimeout="true" xpoweredBy="true"/>
  -->

To change the host and port that the JWSDP Registry Server uses to connect to Xindice, edit the following properties in the <JWSDP_HOME>/jwsdp-shared/bin/launcher.xml file and uncomment them. The host and port must be the same as the Tomcat host and port. 

  <!--
      to change the host and port that the RegistryServer uses to
      connect to Xindice, update the following properties:

      <sysproperty key="org.apache.xindice.host" value="desired Xindice host"/>
      <sysproperty key="org.apache.xindice.port" value="desired Xindice port"/>
  -->

Modifying Tomcat's Default Logging Level

The Java WSDP supports the Jakarta Commons Logging API. By default, the logging level for the technologies in the Java WSDP is set to warn. The following levels are available, in ascending order of granularity: 

  fatal
  error
  warn
  info
  debug
  trace

You can change the default level of logging for Tomcat. For example, to change the default level to debug, specify the following properties in your <JWSDP_HOME>/conf/jwsdp.properties file. 

  org.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
  org.apache.commons.logging.simplelog.defaultlog=debug

Logging output appears in the file <JWSDP_HOME>/logs/jwsdp_log.<date>.txt.

You can set the logging level for more than one logger by specifying additional properties. If applicable, see the release notes for individual technologies to learn how to set the logging level for each technology.

The default logger, SimpleLog, assumes that logger names are hierarchical. To set a default log level for all the technologies with package names beginning with com.sun.xml, you can say: 

  org.apache.commons.logging.log.com.sun.xml=info

You could add another system property definition to specify logging for Tomcat classes. For example, use 

  org.apache.commons.logging.log.org.apache.commons.digester=warn

to receive only warnings from the Digester module that Tomcat uses to parse web.xml files.

For more information about configuring logging, see the Jakarta Commons Logging API documentation. In particular, refer to the Package Description.

Uninstalling Java WSDP 1.3

At some point, you may need to uninstall Java WSDP 1.3:

Known Issues

Click here to display an up-to-date list of known problems with the Java WSDP 1.3 release.

 

Please send feedback on this Java WSDP release to jwsdp-feedback@sun.com.

Copyright © 2003 Sun Microsystems, Inc. All rights reserved.