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.
maven support projects don't have to have a server instance associated when opened in the IDE. When the user selects a server later, any changes to the j2eemoduleprovider implementation are ignored. fireServerChange() fails to do anything because the old Server instance is null ConfigSupportImpl ensureConfigurationReady() fails as well because the Server instance reference is only set in the constructor and never updated. -> IDE restart is necessary for the changes in server settings to apply.
TM -> 6.0
Unfortunately, it is not easy to fix this issue properly. Providing at least a hack to work around the issue: a private J2eeModuleProvider.resetConfigSupport() method will allow to reset the old config support. Checking in src/org/netbeans/modules/j2ee/deployment/devmodules/spi/J2eeModuleProvider.java; /cvs/j2eeserver/src/org/netbeans/modules/j2ee/deployment/devmodules/spi/J2eeModuleProvider.java,v <-- J2eeModuleProvider.java new revision: 1.60; previous revision: 1.59 done RCS file: /cvs/j2eeserver/test/unit/src/org/netbeans/modules/j2ee/deployment/devmodules/spi/J2eeModuleProviderTest.java,v done Checking in test/unit/src/org/netbeans/modules/j2ee/deployment/devmodules/spi/J2eeModuleProviderTest.java; /cvs/j2eeserver/test/unit/src/org/netbeans/modules/j2ee/deployment/devmodules/spi/J2eeModuleProviderTest.java,v <-- J2eeModuleProviderTest.java initial revision: 1.1 done