Community
Participate
Working Groups
Build ID: 4.2 Steps To Reproduce: profile.server.wst.internal.ApplicationServerListener, makes a call to ServerCore.getServers(), this call should be wrapped within a job or moved out of the initialization of the TPTP plugin. Plugin initialization should be fast and simple. The call in the ApplicationServerListener assumes that the server plugin has already been initialized and loaded, which might not be the case. Doing such call, at plugin initialization could cause other plugins to get loaded and delay the loading of the platform. Although 1.5.3 allowed this beahviour, in 2.0 such behaviour will now cause ServerCore.getServer() to throw a initialization exception. If the plugin has not finished its loading. Currently the code for server code is not completed and the startup of ApplicationServerListener, throws a NPE. More information:
Eugene, please update target
sizing updated
TPTP 4_2_1 support up to WTP 1.5.x only. WTP 2.0 is supported since TPTP 4.4. The problem mentioned here is fixed in bug 174886(for WTP2.0) and bug 174863(for WTP1.5.3) ServerCore now loadRuntimesList() and loadServersList() before executeStartups() which triggers ApplicationServerListener in TPTP.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
