Mailing-List: contact dev-help@harmony.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@harmony.apache.org
Received-SPF: pass (herse.apache.org: domain of alexey.v.varlamov@gmail.com
 designates 209.85.132.242 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=be692Q4cjpRL4ADVQ3BaFTeGA6eGAhMuXmPIjskHo8LXN3sNSfJvHVcxOUzONxLDzCvCua/GnH5gPAyi5pkjmS6R8nV723jk8+oA8XvWqCGyFCAQ2dofMXikaTj87Sbux8QkkfsYemkj1xy50E1EgAIhkz5dzMsbeNnoT12NzbQ=
Message-ID: <f944d83d0704240450g2d5eee03nf4f99b779d20257d@mail.gmail.com>
Date: Tue, 24 Apr 2007 18:50:45 +0700
From: "Alexey Varlamov" <alexey.v.varlamov@gmail.com>
To: dev@harmony.apache.org
Subject: Re: [jdktools][jpda] Adapt Eclipse JDI implementation to complete
 JPDA support in Harmony
In-Reply-To: <b6cb498e0704232256v6c2e4f28p513da77b5dd3a003@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <b6cb498e0704200305k2bf7dabft927032cfecc48593@mail.gmail.com>
	 <f982cec50704200355v15950e16g5ccfaea58b068783@mail.gmail.com>
	 <b6cb498e0704232256v6c2e4f28p513da77b5dd3a003@mail.gmail.com>

2007/4/24, Ivan Popov <ivan.g.popov@gmail.com>:
> I've run several experiments with JDI implementation from Eclipse and
> was able to use it for running JDB debugger demo and Netbeans
> debugger. However, there are several issues that should be solved.
>
> 1. Eclipse 3.0 provides quite independent JDI implementation, one can
> use two separate jars from JDT runtime bundle:
>
>  jdi.jar - JDI API interfaces
>  jdimodel.jar - JDI implementation
>
> But it corresponds to 1.4 and works not stable with Netbeans debugger,
> so it is not the case.
>
> 2. In the newer Eclipse 3.2 and 3.3 JDI implementation corresponds to
> 1.5 and works well with both JDB and Netbeans (except of a few issues
> mentioned below). Unfortunately, it introduces dependencies on two
> additional jars (for formatting error messages and NLS support):
>
>  com.ibm.icu.base_3.6.0.20061215.jar - from com.ibm.icu.base bundle
>  org.eclipse.osgi_3.3.0.v20070321.jar - from RCP Runtime Binary bundle
>
> The first one is quite small and independent bundle available from
> Eclipse download site and I think it's OK to add it to Harmony
> together with JDI jars. For the second one an easy stub can be
> implemented to eliminate this dependency.
>
> 3. All Java debuggers expect that JDI API is located in
> JDK/lib/tools.jar and implicitly add it to classpath when debugger is
> started. This means we need to repackage all classes from Eclipse's
> jdi.jar to Harmony's tools.jar. I don't like this solution, but it
> seems the only possible one. I hope there are no legal issues with
> such repackage. All other jars can be added separately and loaded with
> special class loader, similar to what is already implemented for
> Eclipse compiler jar.
>
> 4. There are a few bugs in implementation of JDI connectors which
> throw NPE when are used in JDB and Netbeans debuggers. I fixed this in
> my experiments and fix is rather simple. I can submit bug to Eclipse
> and attach this fix. I hope Eclipse folks can apply it quickly.
>
> If nobody objects I will proceed with items 2-4.

And yes, your effort is very much appreciated ;)


>
> Thanks.
> Ivan
>