Re: [ann] new release 1.0 RC5
Great! Congrats! :-) Best Regards, Antonio Gallardo Thomas Mahler dijo: > 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: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ann] new release 1.0 RC5
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Weird Error in Access with Memo-Fields
Hi, I am using OJB and Access at the moment. So far everything worked fine, and I can also store memofields to the database. Now I integrated my classes in a web-application and there I get a really strange behaviour, when I save my data to the database: A) When I start Tomcat (5.0) and edit an entry and save it everything works fine. The data is written correctly to the database. B) When I try to edit again another or the same entry I get the typical error when the repository_user.xml file is not correctly set up: but all my necessary fiels are set to LONGVARCHAR. The error message is something like that: org.apache.ojb.broker.PersistenceBrokerSQLException: [Microsoft][ODBC Microsoft Access Driver]Die Zeichenfolgedaten wurden rechts abgeschnitten. (null) org.apache.ojb.broker.accesslayer.JdbcAccessImpl.executeUpdate(JdbcAccessImpl.java: 479) org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBrokerImpl.java: 1996) org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java: 1889) org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java: 665) org.apache.ojb.broker.core.PersistenceBrokerImpl.storeCollectionObject(PersistenceBrokerImpl.java: 855) org.apache.ojb.broker.core.PersistenceBrokerImpl.storeCollections(PersistenceBrokerImpl.java: 814) org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBrokerImpl.java: 2007) org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java: 1889) org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java: 665) org.apache.ojb.broker.core.PersistenceBrokerImpl.storeCollectionObject(PersistenceBrokerImpl.java: 855) org.apache.ojb.broker.core.PersistenceBrokerImpl.storeCollections(PersistenceBrokerImpl.java: 814) org.apache.ojb.broker.core.PersistenceBrokerImpl.storeToDb(PersistenceBrokerImpl.java: 2007) org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java: 1889) org.apache.ojb.broker.core.PersistenceBrokerImpl.store(PersistenceBrokerImpl.java: 665) org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersistenceBroker.java: 160) org.apache.ojb.broker.core.DelegatingPersistenceBroker.store(DelegatingPersistenceBroker.java: 160) kos.wnetz.wwnavi.WWEntity.save(WWEntity.java: 285) sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java: no source available) sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 25) What I tried next was to view the behaviour of the PlatformMsAccessImpl class: What I noticed there that the second time the data was about to be store ther was no output of this class (I coded some low level debugging messages). Does anyone know if this is an error of OJB or what am I doing wrong? tino - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat
Hello, I currently have a fairly basic account and I'm considering getting Tomcat functionality added. Can you tell me how Tomcat is configured. I'm particularly interested in database access. Will I have access to server.xml? Thank you, Damon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
