This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
How to reproduce: 1. Deploy to a local instance. 2. Switch to another server instance in the wsp or wsc panel. 3. Deploy to the new instance. 4. In the ant output, you'll see that the ServerProperties is still pointing to the local instance. Note that this can happen randomly depending on whether garbage collection happens before or not. This is due to caching of the amconfig.xml file which for some reason is not up to date.
Need to figure out why the cache AMConfig instance is not up to date.
Checked fixes into release55_dev branch. IDE:------------------------------------------------- IDE: [10/10/06 9:09 PM] Committing "Identity Profile API" started Checking in AMConfigManager.java; /cvs/identity/profileapi/src/org/netbeans/modules/identity/profile/api/configurator/impl/file/Attic/AMConfigManager.java,v <-- AMConfigManager.java new revision: 1.1.2.7.2.3; previous revision: 1.1.2.7.2.2 done IDE: [10/10/06 9:09 PM] Committing "Identity Profile API" finished IDE: [10/10/06 9:09 PM] Diffing "AMConfigManager.java" finished
The issue here is that the path string used to look up the AMConfig from the cache may contain a mixture of forward and backward slashes depending on whether it's coming from the deploy task or the ui panel. That cause multiple instances of the same AMConfig to be cached resulting in inconsistent values. The fix is to normalize the path string used to look up the AMConfig from the cache.
changes reviewed and checked into release55 branch.
closed the wrong one.
change back to the old status.
Tested with EP build20061015 and have not seen the problem. Close the bug.