When you connect to a source control system, PowerBuilder instantiates a Java VM by default. For certain source code control (SCC) programs, such as Borland’s StarTeam or Serena’s TrackerLink, the Java VM instantiated by PowerBuilder conflicts with the Java VM instantiated by the SCC program. To prevent Java VM conflicts, add the following section and parameter setting to the PB.INI file:
[JavaVM]
CreateJavaVM=0
This prevents PowerBuilder from instantiating a Java VM when it connects to a source control system.
If you include this parameter setting in your PB.INI file and your source control system requires a Java VM, the source control system typically initializes the Java VM used by PowerBuilder on connection of the workspace to source control. The Java VM must have PowerBuilder in its classpath; otherwise you will not be able to deploy JSP targets from this workspace. PowerBuilder must exit to unload a Java VM. To successfully deploy JSP targets, you must first disconnect the current workspace from source control, then close and reopen PowerBuilder without reconnecting to source control. You can reconnect the workspace to the source control system after you deploy JSP targets.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
