Mailing-List: contact open-jpa-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: open-jpa-dev@incubator.apache.org
Received-SPF: pass (asf.osuosl.org: domain of awhite@bea.com designates
 63.96.176.25 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <7D856CDFE035FF45A0420ACBD71BDD630243156C@repbex02.amer.bea.com>
References: <7D856CDFE035FF45A0420ACBD71BDD630243156C@repbex02.amer.bea.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <728AE190-1629-4C9F-A240-6673F0EC14B7@bea.com>
Content-Transfer-Encoding: 7bit
From: Abe White <awhite@bea.com>
Subject: Re: svn commit: r465623 - in
 /incubator/openjpa/trunk/openjpa-persistence-jdbc/src/test/java/org/apache/openjpa/persistence/generationtype:
 ./ IdentityGenerationType.java TestGenerationType.java
Date: Thu, 19 Oct 2006 12:50:40 -0700
To: open-jpa-dev@incubator.apache.org

> [ x] Separate setUp() and tearDown()
> [ ] Separate setUp() and tearDown(), but setUp() invokes tearDown()
> [ ] Typically no tearDown(); put cleanup logic in setUp()
> [ ] Other. Please describe.

IMO, if we're diligent in writing proper tearDown methods, there's no  
reason to put the tearDown logic in setUp.  The only reason we got  
into that habit in Kodo was that we were sloppy with our test case  
cleanup.
_______________________________________________________________________
Notice:  This email message, together with any attachments, may contain
information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated
entities,  that may be confidential,  proprietary,  copyrighted  and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.