JDK-4287596 : JPDA pluggable connections and transports
  • Type: Enhancement
  • Component: core-svc
  • Sub-Component: debugger
  • Affected Version: 1.4.0,1.4.2
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 1999-11-03
  • Updated: 2017-05-16
  • Resolved: 2003-07-18
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
5.0 tigerFixed
Related Reports
Duplicate :  
JDK-4635423 - JDWP: usage of perror() in socketTransport.c is not helpful
Relates :  
JDK-4810155 - Need a way to timeout or test for connection with ListeningConnector.accept()
Relates :  
JDK-4449399 - JDI: add an extensibility mechanism
Description

Name: ab88733			Date: 11/03/99




This feature involves the ability to create a custom transport between the back
and front ends of the multi-layered JPDA technology.  Such a transport could be
infrared, a serial cable, or other types of connections.  This feature involves
only putting APIs to allow custom transports, and not developing any custom
transports.
======================================================================
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b12
14-06-2004
PUBLIC COMMENTS .
10-06-2004
EVALUATION Must be added so that third parties can add connectprs or transports. robert.field@Eng 1999-11-23 Would like to see understanding of tools companies and other licensees who have requested this feature and an understanding of how we will work with them in defining and testing of the feature. david.biagini@Eng 2000-01-13 This feature will allow some licensees, such as Symbian (Nokia, Ericson, Motorola, etc) to debug their applications on their embedded devices. It's been requested by their licensee support engineer several months ago. Being that it's just an API that others can write custom code for their configurations, little work with them is neccesary - we just need to define the hooks so that they can plug in a custom module and then debug their code. andrew.bennett@eng 2000-01-19 This feature has been implemented for tiger. Specifically, JDI now has a provider mechanism so that 3rd party Connectors can be developed and deployed. Additionally, TransportServices can be developed and deployed. JDI will encapsulated any installed TransportService implementations with attaching and listening Connectors. On the debuggee-side a native transport interface has been defined so that 3rd party transport libraries can be loaded by the JDWP agent. ###@###.### 2003-07-09
09-07-2003