| IP.com Number | IPCOM000012903D |
|
|
|---|---|---|---|
| Dated | Jun 9, 2003 UTC | ||
| Size | 1 page(s) (40.5 KB) | ||
| Disclosed by |
|
||
| Country | |
|---|---|
| Language | English (United States) |
This document was submitted to IP.com's Prior Art Database and this preview is designed to provide you with information regarding the contents of this document by displaying up to the first four pages of the document as scaled page renderings and displaying a limited amount of text which was extracted from the document on the Text Preview Tab.
To find out more on how to obtain the entire document, click the Download tab. There is a charge for downloading some Prior Art Database documents; please examine carefully whether you believe this document fills your needs before purchasing.
For more information about the Prior Art Database, visit the Learn section of this website. Thank you for visiting IP.com's Prior Art Database! You may wish to check out our Global Patent Search website before you leave.
Simplify use of Java Platform Debugger Architecture to debug remote Java programs
Typically developers of RPG/COBOL programs familiar with use of green-screens face significant hurdles when moving to a web-based Java Development Platform.
The Eclipse Integrated Development Environment (IDE) provides a generic way to debug remote Java programs. However, IDE requires several cumbersome interrelated steps and there is a need to replace these with one step.
Java Platform Debugger Architecture (JPDA) is supported by the Eclipse based IDE.
Eclipse based IDE implements Java Debug Interface ( JDI ). Users can connect to, and debug any remote application running on a remote Java Virtual Machine Debugger Interface ( JVMDI ) which is compliant with VM through IDE. However the generic way to use JDI is cumbersome for typical iSeries legacy program developers. The typical scenario includes the steps of: Go to iSeries "green-screen" to start class in remote VM. Java Debug Wire Protocol (JDWP) port and tedious options must be specified. This causes execution of the program to halt until a connection is established with debug client on this port. IDE debugger client is then started which tries to connect to the above specified port.
Once a connection is sensed, the remote class starts to run until a breakpoint is hit, or the program terminates.
The disclosed idea effectively automates the whole process described above. The debugging of remote Java program on iSeries from IDE is...
Copyright © 2004-2010 IP.com. All Rights Reserved.