Compatibility Issues

Deploytool

Deploytool is no longer be available. The equivalent functionality is available in the NetBeans IDE. For more information and to plan a migration, please see J2EE 1.4 tutorial for NetBeans 4.1 at http://www.netbeans.org/kb/41/j2ee-tut/index.html.

Verifier

• Verifier GUI mode (invoked by verifier -u) is no longer be available. The equivalent functionality will be available in the NetBeans IDE.

• The default mode for application verification when using verifier tool has been changed from “Verify J2EE Rules” to “Verify J2EE Rules and Sun Application Server Configuration Rules.” In other words, by default verifier tests whether an application meets J2EE rules and is configured to run on Sun Application Server. The verifier command contains a command-line switch to test an application for J2EE rules only.

Classloader Changes

In the current release, the JAR and directory entries added to classpath-prefix, server-classpath, and classpath-suffix attributes of domain.xml (application server configuration file) are available in the JVM system classpath. An application depending on this behavior might be using the following methods from the class java.lang.ClassLoader to access classes or other resources from the JVM system classpath:

• getSystemClassLoader()

• getSystemResource()

• getSystemResourceAsStream()

• getSystemResources

In the next major release, the JAR and directory entries added to classpath-prefix, server-classpath, and classpath-suffix will no longer be available in the JVM system classpath. If an application uses one of the previously mentioned methods, Sun strongly recommends using an equivalent method that does not assume that the resources are available in the system classpath. The equivalent methods that do not rely on the JVM system classpath are available in java.lang.ClassLoader and should be used when possible, for example:

Example 2–1 Old Code

java.net.URL url = ClassLoader.getSystemResource
("com/acme/tools/tools.properties");

Example 2–2 Suggested Change

java.net.URL url = this.getClass().getClassLoader().getResource
("com/acme/tools/tools.properties");

If you cannot change the code, then you can choose to use a new configuration option that will be added in the next release to set the JVM system classpath.

Web Service Security Configuration

Security for Web services can be configured by using the files wss-client-config.xml and wss-server-config.xml. Note that the content and names of these configuration files are unstable and likely to change. The equivalent functionality will continue to be available.