Deployment tools Release Notes

© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Release notes

1.0 Description
2.0 Limitations
3.0 Known problems and workarounds
   3.1 The server does not pick up the changes to a Java file

1.0 Description

This release notes file contains late-breaking information about limitations and known problems and workarounds for the WebSphere® Integration Developer deployment tools and WebSphere test environment.

2.0 Limitations

None

3.0 Known problems and workarounds

3.1 The server does not pick up the changes to a Java file

In WebSphere Integration Developer 6.0.1, projects published to a WebSphere Process Server or ESB server that were configured to run with resources in the workspace did not have to be published to synchronize changes with Java™ resources in the published application. Instead, the server automatically recognized the change to the generated class files and restarted the application on the server, sometimes causing unwelcome behavior.

For example, if the application recycle by the server occurred during a clean build of the workspace, the application might not have finished rebuilding, and its restart might have caused failures in the server process.

In WebSphere Integration Developer 6.0.2, applications published to a WebSphere Process Server or ESB server with resources on the workspace will not be automatically restarted when Java resources change. If the change to a Java file occurs in an application that is published to a server with auto-publish enabled, then WebSphere Integration Developer will automatically cause the server to restart the application. If the change to a Java file occurs in an application that is published to a server with auto-publish disabled, which is the default, then a warning will appear in the Problems view to inform you that the application must be restarted on the affected server. In the latter case, you may republish the application manually from the Server view, use the quick fix associated with the problem marker on the application project, or rely on the component test framework to take the corrective action when you initiate a component test.