Return-Path: Delivered-To: apmail-incubator-harmony-commits-archive@www.apache.org Received: (qmail 68981 invoked from network); 7 Nov 2006 17:41:20 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Nov 2006 17:41:20 -0000 Received: (qmail 424 invoked by uid 500); 7 Nov 2006 17:41:30 -0000 Delivered-To: apmail-incubator-harmony-commits-archive@incubator.apache.org Received: (qmail 388 invoked by uid 500); 7 Nov 2006 17:41:30 -0000 Mailing-List: contact harmony-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: harmony-dev@incubator.apache.org Delivered-To: mailing list harmony-commits@incubator.apache.org Received: (qmail 347 invoked by uid 99); 7 Nov 2006 17:41:30 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Nov 2006 09:41:30 -0800 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Nov 2006 09:41:14 -0800 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 04FF67142F5 for ; Tue, 7 Nov 2006 09:40:52 -0800 (PST) Message-ID: <13772931.1162921252017.JavaMail.jira@brutus> Date: Tue, 7 Nov 2006 09:40:52 -0800 (PST) From: "Alexei Zakharov (JIRA)" To: harmony-commits@incubator.apache.org Subject: [jira] Commented: (HARMONY-1992) [classlib][beans] new fixes for DefaultPersistenceDelegate failures (3) In-Reply-To: <5749539.1161971116656.JavaMail.root@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ http://issues.apache.org/jira/browse/HARMONY-1992?page=comments#action_12447868 ] Alexei Zakharov commented on HARMONY-1992: ------------------------------------------ When I remove DefaultPersistenceDelegate test from the exclude list another beans test - IntrospectionExceptionTest - starts to hang on the DRLVM DEBUG build. So I'm preserving the current exclude list state until the DRLVM issue is fixed. > [classlib][beans] new fixes for DefaultPersistenceDelegate failures (3) > ----------------------------------------------------------------------- > > Key: HARMONY-1992 > URL: http://issues.apache.org/jira/browse/HARMONY-1992 > Project: Harmony > Issue Type: Improvement > Components: Classlib > Environment: winXP > Reporter: Alexei Zakharov > Assigned To: Alexei Zakharov > Attachments: HY1992-DefaultPersistenceDelegate.patch, HY1992-DefaultPersistenceDelegateTest.patch > > > The attached patch fixes the following tests from the org.apache.harmony.beans.tests.java.beans.DefaultPersistenceDelegateTest class: > testInitialize_NormalBeanInfo > testInitialize_SameInstance > testInitialize_TransientProperty > testInitialize_NullEncoder > These tests were refactored. All references to CallVerificationStack class were removed (as it was decided in the mailing list) and replaced with much more lightweight technique. During enabling of these tests I found that RI uses a bit different model for DefaultPersistenceDelegate#initialize() (and probably for other methods) and stores a lot of extra statements to the output stream. From the spec point of view these statements are not really required. I've decided to keep the current model for now and just hack the tests to satisfy both models (ours and RI's). However, if during enabling of some real applications it turns out that we need so follow the RI's model I promise to get back to this. > testInitialize_NotRegularGetter > Deleted since the logic is the same with the testInitialize_NormalBeanInfo test > testInitizalize_Normal > The test was reworked, extra test logic was added. > Now all tests pass on Harmony. So we can remove DefaultPersistenceDelegateTest from exclude list. BTW, there are still two valid failures on RI. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira