Why is the local port in a run configuration? Picture this scenario, which is impossible with port being per run config.
- App server can bind to multiple ports and hosts
- User selects what port a particular webapp is to run on.
This used to be possible by having a custom deployment panel for the web module, to allow the user to select the appropriate port/website to 'mount' the webapp on. Of course, this is still possible. However, the introduction of a global local port concept (1 per run instance) makes it impossible to have a sane UI to support the above scenario.
So I suggest that this method be removed (getLocalPort), and instead let the plugin itself display the appropriate textfield or whatever it wants for local port, so it has the choice of putting it in the web deployment panel or in the main config panel.