Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 48108 invoked from network); 15 Dec 2003 19:22:09 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 15 Dec 2003 19:22:09 -0000 Received: (qmail 87512 invoked by uid 500); 15 Dec 2003 19:21:59 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 87479 invoked by uid 500); 15 Dec 2003 19:21:59 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 87465 invoked from network); 15 Dec 2003 19:21:58 -0000 Received: from unknown (HELO mailout03.aul.t-online.de) (194.25.134.81) by daedalus.apache.org with SMTP; 15 Dec 2003 19:21:58 -0000 Received: from fwd11.aul.t-online.de by mailout03.aul.t-online.de with smtp id 1AVyI6-0004Dc-03; Mon, 15 Dec 2003 20:22:02 +0100 Received: from code-au-lait.de (rX-OGoZVger313z3kgRZBr+lDZyBdBPovIrS-5wtxro-QXpTmRlQ0i@[80.145.111.45]) by fmrl11.sul.t-online.com with esmtp id 1AVyHn-0T38LI0; Mon, 15 Dec 2003 20:21:43 +0100 Message-ID: <3FDE09C3.1000303@code-au-lait.de> Date: Mon, 15 Dec 2003 20:21:39 +0100 From: Armin Waibel User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031013 Thunderbird/0.3 X-Accept-Language: en-us, en MIME-Version: 1.0 To: OJB Developers List Subject: Re: [ann] new release 1.0 RC5 References: <3FDCD03E.7070603@web.de> <6.0.1.1.2.20031215095825.02c8e578@localhost> In-Reply-To: <6.0.1.1.2.20031215095825.02c8e578@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Seen: false X-ID: rX-OGoZVger313z3kgRZBr+lDZyBdBPovIrS-5wtxro-QXpTmRlQ0i@t-dialin.net X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi David, seems you are using JCA 1.5, but OJB only use 1.0 regards, Armin David Forslund wrote: > I downloaded the source for RC5 and did a build which worked fine (after > loading j2ee.jar and jdo.jar into the lib directory). I also did a > build junit > which worked, but when I tried a build jar, it fails with the following: > > main-opt: > [javac] Compiling 580 source files to > C:\Java\db-ojb-1.0.rc5\target\classes > [javac] Note: Some input files use or override a deprecated API. > [javac] Note: Recompile with -deprecation for details. > [javac] Compiling 242 source files to > C:\Java\db-ojb-1.0.rc5\target\classestest > [javac] Compiling 10 source files to > C:\Java\db-ojb-1.0.rc5\target\classesjca > [javac] > C:\Java\db-ojb-1.0.rc5\target\srcjca\org\apache\ojb\otm\connector\OT > MJCAManagedConnectionFactory.java:79: > org.apache.ojb.otm.connector.OTMJCAManagedConnectionFactory is not > abstract and does not override abstract method > setResourceAdapter(javax.resource.spi.ResourceAdapter) in > javax.resource.spi.ManagedConnectionFactory > [javac] public class OTMJCAManagedConnectionFactory > [javac] ^ > [javac] 1 error > > BUILD FAILED > file:C:/Java/db-ojb-1.0.rc5/build.xml:260: Compile failed; see the > compiler erro > r output for details. > > Total time: 3 minutes 6 seconds > > Is there some dependency I'm missing in using jar as the target? > > Dave > > > At 02:03 PM 12/14/2003, Thomas Mahler wrote: > >> Dear all, >> >> After a long time of preparation we finally managed to assemble a new >> release of OJB. >> >> We fixed a lot of bugs and we also improved the performance for all APIs. >> >> This is the last release candidate for 1.0. If no major bugs are >> detected within the next two weeks this release will be relabled as 1.0. >> We will provide a maintenance branch to provide those users with fixes >> who wish to stay with a frozen 1.0 version. No new features will be >> implemented in the maintenance branch. >> >> All new features and enhancements will be made in a new 1.1 branch. >> >> Thanks to everyone who helped to make this happen! >> >> from the release notes: >> >> ObJectRelationalBridge (OJB) is an Object/Relational mapping tool that >> provides transparent transactional persistence for Java Objects against >> relational databases. OJB provides ODMG and JDO interfaces. >> >> --------------------------------------------------------------------- >> Release 1.0 rc5 >> --------------------------------------------------------------------- >> >> This is the last planned rc before the 1.0 release. If there are no major >> bugs this release will be relabled as 1.0 after two weeks. >> >> NEW FEATURES: >> - With this release we are feature complete for the 1.0 release! >> For 1.0 you should not expect more features to be added. >> >> NOTES: >> - slight changes in repository.dtd, OJB.properties were made >> >> - internal kernel interface method signature changed: >> in JdbcAccess two method signatures change >> in StatementManagerIF one method signature change >> These changes are necessary to fix a "design bug" in handling >> of jdbc type metadata. See discussion on dev-list "[VOTE] Design bug >> fixed - check in?" >> >> - ObjectCache implementation classes constructor arguments change. We >> now pass a Properties argument too. Allows to set configuration >> properties >> for each ObjectCache instance >> >> - changed the JDORI plugin to now use the latest 1.0.1 version of the >> JDO reference implementation. >> >> - OJB is now very strict in handling RsIterator instances. RsIterator is >> bound very closely to the used PersistenceBroker instance. >> Thus if you do a >> PersistenceBroker#close >> PersistenceBroker#commitTransaction >> PersistenceBroker#abortTransaction >> call, the current RsIterator instance resources will be >> cleaned up automatic >> and invalidate current instance. >> >> CHANGES: >> - add possibility to declare ObjectCache implementation on >> class-descriptor >> and jdbc-connection-descriptor level (means per class and per database >> connection) too >> >> - add a new interface called org.apache.ojb.odmg.TransactionExt >> to make additional proprietary methods available for user by >> casting org.odmg.Transaction to TransactionExt >> >> - behaviour of org.odmg.Transaction#checkpoint() changed. Now the >> database transaction was commited when checkpoint was called, seems this >> is more in unison with ODMG spec: >> " Calling checkpoint commits persistent object modifications made >> within the >> transaction since the last checkpoint to the database." >> If you want to flush persistent object >> modifications made within the ODMG transaction to the underlying database >> transaction without commit the changes (old behaviour of checkpoint()), >> please cast Transaction to TransactionExt and use new method flush(). >> >> - make odmg collections pluggable via OJB.properties file >> >> - Restructuring and further enhancements of the documentation. >> >> >> BUG FIXES: >> >> Please refer to our Bug tracking site under >> http://scarab.werken.com/scarab/issues/id/OJBxxx to see details for a bug >> with id OJBxxx. >> >> - fix ClassLoader problem when merging DescriptorRepository instances >> >> - fixed the JDORI problems with loading object via extend based queries. >> now objects are brought under JDO control and equipped with a >> statemanager >> in the load process. >> >> >> enJoy the new release, >> Thomas >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: ojb-user-unsubscribe@db.apache.org >> For additional commands, e-mail: ojb-user-help@db.apache.org > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org > For additional commands, e-mail: ojb-dev-help@db.apache.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org