search

coherence-community / oracle-bedrock

Oracle Bedrock
Other
55 stars 31 forks source link

Refactor RemoteDebugging Option to be a Profile #157

Closed brianoliver closed 8 years ago

brianoliver commented 10 years ago

Currently RemoteDebugging is a hard-coded Java-based Option, the Option implementation itself carrying state. Instead it should be a RemoteDebugging Profile (that also implements the Option interface), which includes the necessary interceptors to enable, disable and configure remote debugging for Java applications.

Ultimately this will replace (and thus break applications using) the RemoteDebugging option, but importantly it will isolate (refactor) the current remote debugging code into a single class.

brianoliver commented 10 years ago

@brianoliver said: This may be a little involved as it requires a two-phase approach to using the Option.

Phase 1: To produce the JVM option string (for the Local process) Phase 2: To wait for a connection back to the JVM from a port defined by the option.

brianoliver commented 8 years ago

This issue was imported from JIRA ORACLETOOLS-157

brianoliver commented 10 years ago

Reported by @brianoliver

brianoliver commented 8 years ago

Marked as fixed by @brianoliver on Monday, February 15th 2016, 3:56:53 pm