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.
To improve debugging of JavaFX applications a new FXJDI proxy has been introduced. By default the proxy will delegate on standard JDI, providing JavaFX specific behavior in certain cases: - name mangling/de-mangling - handling of lazy binding - removing synthetic frames The proxy is supposed to be compatible with java applications. FXJDI provides additional connectors - they simply delegate on existing connectors. We need a way how to specify exact connector instead of just taking first one which implements given transport.
Created attachment 98382 [details] suggested patch
The patch looks O.K., I'm going to integrate it...
Created attachment 98822 [details] better patch patch to better handle current implementation of fxjdi - lookup should look for Connector class rather than ListeningConnector.
I've already committed the first patch as changeset: 170616:62c87fcb4fde http://hg.netbeans.org/main/rev/62c87fcb4fde The second patch just looks for objects implementing Connector and then extracts those that implement ListeningConnector. This looks strange, why is it needed?
Using Connector class in the Lookup in changeset: 170633:8dc8766b7183 http://hg.netbeans.org/main/rev/8dc8766b7183
Integrated into 'main-golden', will be available in build *201005132200* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/ User: Log: