Community
Participate
Working Groups
Build ID: wtp 2.0 Steps To Reproduce: Recently, RuntimeBridge has been moved from jst.server.core to wst.server.core. And it is missing the below code in getRuntimeComponents(). This causes runtime container is not returned. RuntimeClasspathProviderWrapper rcpw = JavaServerPlugin.findRuntimeClasspathProvider(runtime.getRuntimeType()); if (rcpw != null) { IPath path = new Path(RuntimeClasspathContainer.SERVER_CONTAINER); path = path.append(rcpw.getId()).append(runtime.getId()); properties.put(CLASSPATH, path.toPortableString()); } ref: 00303067 More information:
WST does not depend on JDT so that code still exists as an extension in the JST layer. Since this is working for all the other server adapters I'll need more information on exactly what is failing to diagnose the problem.
Discussed offline. The problem is that the adopter had created a copy of org.eclipse.jst.server.core.internal.RuntimeClasspathProvider to extend the default classpath provider. In the previous release RuntimeClasspathProvider depended on a string named 'classpath' to be provided by the RuntimeBridge in the runtime's component properties. Now that the bridge has been moved down to WST, it no longer has access to the runtime's classpath. As a result, the 'classpath' property no longer exists and the RuntimeClasspathProvider computes the classpath directly, breaking the copied version. This bug will be used to create declared API in WTP 3.0 for obtaining and extending facet runtime components so that it is no longer required to use internal methods or property names and this problem does not happen again.
*** Bug 189211 has been marked as a duplicate of this bug. ***
Ran out of time, retargeting for next release.
As part of an effort in improving quality, we are reviewing all bugs opened before June 1st, 2008, where the severity is set to "Major" or higher; and the bug does not contain a targeted milestone. When reviewing the bugs, this bug was identified with the above qualities. Review this bug and update according the following options: * Target to a specific release. Specify "future" if you are planning to fix it, but not in the next release * Adjust severity as appropriate
Given that this is an extremely old bug and there is no activity for 4 years, I am marking this one as no plan to fix.