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.
I file this bug here and not under the sun/appserv or tomcatint modules because I believe the solution has to come from the j2eeserver side. The problem: * Have a running Sun AppServer configured in NB. * Add another running Tomcat 5.5, but with a wrong user/password combination. * Try to expand that Tomcat node. You will get a http authentication dialog from the appserv plugin:-( * At least two problems: - That dialog might change the user/password for a configured Sun AppServer:-( - It does NOT change the properties for the Tomcat instance in question:-( I know, the java.net.Authenticator is really bad:-( So the only solution, I see is a central `Authendicator' registry where the plugins (and possibly other parts of the IDE) can register `extended' Authendicators. I mean extended, because they should save their last state (wasCalled, username/password). So the plugins would register one of those extended Authenticators before a HTTP (or similar) request and unregister it afterwards. Before they unregister it, they could ask if it was called and if so, update their properties accordingly. If there was no extended Authenticator registered for a particular host/port, the Registry would use a generic Dialog.
We have been thinking about this for some time, but we didn't have time to implement it so far. *** This issue has been marked as a duplicate of 46123 ***