Test and deployment tools - release notes


1.0 Supported software and specifications
2.0 Limitations
   2.1 Universal Test Client Namespace Limitations
3.0 Known problems
   3.1 Server Target Validation

1.0 Supported software and specifications

In this release, the following run-time environments are supported:

2.0 Limitations

2.1 Universal Test Client Namespace Limitations

The UTC (Universal Test Client) can only be used to test applications running on a server within a single Java namespace. When multiple classes exist with the same package and class names, only one of these classes will be available for testing in the UTC. There are two workarounds for this problem:

  1. If the conflicting namespace is within two or more separate enterprise applications, deploy the applications to two or more separate servers. The UTC on each server will now be able to test the applications separately.
  2. Change the namespace (package name or class name) of the conflicting classes so that they do not conflict. One example of this is a Web Service proxy class for an EJB generated into the same EAR. In this case you can use the custom mapping settings to ensure that the Web Service classes are generated into a different package.

3.0 Known problems

3.1 Server Target Validation

When you target a project to one server type and run on a different server type (which may have incompatibilities with each other), you will not receive any errors during publish or startup. It is your responsibility to make sure that the targeted server and deployed server are matched or compatible.

Return to the main readme file