Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: neutral (asf.osuosl.org: local policy)
Message-ID: <01a501c65a81$e4c0f610$c900a8c0@neosur.com>
From: "Daniel Gandara" <danielgandara@neosur.com>
To: <harmony-dev@incubator.apache.org>
Subject: [rmi] getting 1.4 bytecode
Date: Fri, 7 Apr 2006 17:28:54 -0300
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit

Hi, 
    As discussed with Oliver, I built the rmi code with the 
-target jsr14 option and I got a 1.4 bytecode for the package.    
I run our test suit against the package and it seems to work ok.   

This is a sum up of the experience:
1) -target jsr14 option only worked with Sun's compiler, I 
    could not make it work on Eclipse...
2) I had to make changes to the code, basically I had to 
    change enums and change/remove java.util.concurrent 
    classes we use (ConcurrentHashMap and 
    ThreadPoolExecutor)

note: there is obviously a performance penalty due to 2).

The question I have now is if I should send this modified code 
to be used in Harmony during this transitional phase or not.  
What do you think?

I'll be waitting for comments, 

Daniel 


---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org